Value Ladder Architect

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 2515ce9634da · 15 Oct 2026Report an issue or request a re-scan

• PublisherAffitor GitHub organizationOwner of the repository this skill is read from
• Source folderAffitor/affiliate-skills/skills/landing/value-ladder-architectThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict2515ce9634daA new audit runs when the source changes
• Repository statusNot archivedLast push 2 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Design the complete free-to-premium value ladder for affiliate promotions. Triggers on: "value ladder", "customer journey", "upsell path", "ascension model", "free to paid funnel", "tripwire offer", "upsell strategy",…

---
name: value-ladder-architect
description: >
  Design the complete free-to-premium value ladder for affiliate promotions.
  Triggers on: "value ladder", "customer journey", "upsell path", "ascension model",
  "free to paid funnel", "tripwire offer", "upsell strategy", "downsell",
  "product ladder", "price ladder", "customer ascension", "funnel architecture",
  "map my funnel", "design my funnel stages", "monetization path".
license: MIT
version: "1.0.0"
tags: ["affiliate-marketing", "landing-pages", "conversion", "offers", "value-ladder", "pricing"]
compatibility: "Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent"
metadata:
  author: affitor
  version: "1.0"
  stage: S4-Landing
---

# Value Ladder Architect

Design the complete free → tripwire → core → upsell path for affiliate promotions. Maps the entire customer ascension journey, where each step delivers standalone value while naturally leading to the next. The value ladder IS the page sequence: squeeze → bridge → sales → upsell.

## Stage

S4: Landing — The value ladder defines the sequence of pages and offers. Each rung is a landing page, email, or content piece that converts the visitor to the next level.

## When to Use

- User wants to map the entire customer journey, not just one landing page
- User asks about upsells, downsells, tripwires, or funnel stages
- User wants to maximize lifetime value from affiliate promotions
- User says "value ladder", "customer journey", "ascension", "funnel architecture"
- After running `grand-slam-offer` to design the core offer and wanting to expand
- User promotes a product with multiple tiers (free, pro, enterprise)

## Input Schema

```yaml
product:                      # REQUIRED
  name: string                # Product name
  pricing_tiers: object[]     # Available pricing tiers
    - name: string            # e.g., "Free", "Pro", "Enterprise"
      price: string           # e.g., "$0", "$49/mo", "$199/mo"
      features: string[]      # Key features at this tier
  reward_value: string        # Your commission
  reward_type: string         # "recurring" | "one-time" | "tiered"
  url: string                 # Affiliate link

your_assets: string[]         # OPTIONAL — content/resources you already have
                              # e.g., ["blog", "email list", "YouTube channel", "templates"]
                              # Default: ["blog"]

goal: string                  # OPTIONAL — "first_commission" | "maximize_ltv" | "build_list"
                              # Default: "first_commission"
```

**Chaining from S4 grand-slam-offer**: Use `offer_stack` to position the core offer in the ladder.
**Chaining from S4 bonus-stack-builder**: Use `bonus_stack` to populate tripwire and bonus tiers.

## Workflow

### Step 1: Gather Context

1. Map the product's pricing tiers and commission structure
2. Identify user's existing assets (blog, list, social following)
3. Determine goal: first commission (simple ladder) vs maximize LTV (complex ladder)

### Step 2: Design the Ladder

Read `shared/references/offer-frameworks.md` for the Value Ladder framework.

Map each rung:

**Rung 0: FREE (Awareness)**
- What: Blog post, social content, free tool, lead magnet
- Goal: Build trust, capture email, demonstrate expertise
- Skills used: S2 Content, S3 Blog
- Conversion to next rung: Lead magnet opt-in or email capture

**Rung 1: TRIPWIRE ($1-$49, impulse buy)**
- What: Your low-cost asset (template pack, mini-course, audit)
- Goal: Convert from reader to buyer, get email if not captured
- Skills used: `bonus-stack-builder` for asset ideas, `squeeze-page-builder` for page
- Conversion to next rung: Email sequence recommending the core product

**Rung 2: CORE (main affiliate product)**
- What: The affiliate product at its most popular tier
- Goal: Primary commission — solve their main problem
- Skills used: `grand-slam-offer`, `landing-page-creator`
- Conversion to next rung: Product usage → ready for premium tier

**Rung 3: UPSELL (premium tier or complementary product)**
- What: Higher tier of same product, or complementary affiliate product
- Goal: Maximize lifetime value, earn larger commission
- Skills used: `landing-page-creator` (comparison), `email-drip-sequence`
- Conversion: Ongoing value through content → repeat customer

### Step 3: Map the Page Sequence

For each rung, specify:
- Page type (blog post, squeeze page, bridge page, landing page, email)
- Traffic source (organic, social, email, paid)
- Affiliate skill to build it
- Conversion mechanism (CTA, email opt-in, checkout)
- Expected conversion rate benchmark

### Step 4: Design Transition Triggers

Define what moves a person from one rung to the next:
- Rung 0→1: Downloaded lead magnet → email sequence pitching tripwire
- Rung 1→2: Purchased tripwire → immediate upsell page OR email sequence
- Rung 2→3: Used product for X days → email about premium features

### Step 5: Output

Present the complete value ladder with implementation roadmap.

### Step 6: Self-Validation

- [ ] Each rung delivers standalone value (P4 principle)
- [ ] Transitions feel natural, not forced
- [ ] The affiliate product is the CORE (Rung 2), not the upsell
- [ ] Free content (Rung 0) is genuinely helpful, not just a teaser
- [ ] Implementation order is realistic (start simple, add rungs over time)
- [ ] FTC disclosure at every rung with affiliate links

## Output Schema

```yaml
output_schema_version: "1.0.0"
value_ladder:
  product_name: string
  total_rungs: number
  rungs:
    - level: number           # 0, 1, 2, 3
      name: string            # "Free", "Tripwire", "Core", "Upsell"
      offer: string           # What they get
      price: string           # Price point
      page_type: string       # "blog" | "squeeze" | "bridge" | "landing" | "email"
      skill_to_build: string  # Which affiliate skill creates this page
      conversion_to_next: string  # How they move to next rung
      estimated_conversion: string # Benchmark con

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

1. 2026-10-15
   ✓SAFE B 89 / 100

   first audit · source 2515ce9634da

Questions about Value Ladder Architect

• github.com/Affitor/affiliate-skills/tree/main/skills/landing/val — the audited source at commit 2515ce9634da and every finding aboveObserved · 15 Oct 2026

Spotted something wrong? Report a correction · Methodology