/productize

name: productize
description: Turn services into scalable products and build an offer ladder with upsells and downsells. Use when income depends on time, you want leveraged or recurring revenue, or you want multiple price points. Covers service productization, offer ladder (entry/core/premium), and upsell/downsell design — outputs PRODUCTIZATION.md, OFFER_LADDER.md, REVENUE_FLOW.md.

Skill: Productization & Scaling System (Hormozi-Style)

Purpose

Turn skills and services into scalable offers, then organize them into a system that maximizes revenue per customer.

This skill:

• transforms time-based work into leveraged products
• builds an offer ecosystem (ladder)
• increases lifetime value through upsells and downsells

Goal: make more money from the same customer with less effort over time.

---

When to Use

Activate this skill when:

• you sell services and want to scale
• income depends on your time
• you want recurring or leveraged revenue
• you want multiple price points
• you want to increase revenue per customer

---

Inputs

This skill works with:

• an `OFFER.md`
• a service or consulting business
• a program or course
• an existing offer stack
• target audience

---

PART 1: Service → Product Skill

Purpose

Turn services into scalable, repeatable offers.

---

Core Idea

Move from:

• time-based → system-based
• custom → standardized
• manual → repeatable

---

Assistant Behavior

1. Analyze current service

Identify:

• what is being done
• how it is delivered
• how much customization exists
• where time is spent

---

2. Extract repeatable components

Find:

• steps that repeat
• frameworks used
• templates already created
• common problems solved

---

3. Standardize the process

Turn:

• custom work → defined steps
• loose delivery → structured system

Example:

• “I help clients grow” → “3-step growth system”

---

4. Choose product format

Options:

Program (DWY)

• structured guidance
• calls + support
• repeatable delivery

Course (DIY)

• self-paced
• content-based
• scalable

Toolkit / Product

• templates
• systems
• assets

---

5. Decide level of involvement

Choose:

• DIY → lowest involvement
• DWY → medium involvement
• DFY → highest involvement

---

6. Build productized version

Define:

• clear outcome
• step-by-step system
• delivery format
• support level

---

7. Simplify and remove complexity

Ensure:

• fewer steps
• clear path
• easy onboarding

---

Output Format

# PRODUCTIZATION.md

## 1. Current Service
- What is offered
- How it is delivered

## 2. Repeatable Components
- Steps
- Frameworks
- Templates

## 3. Productized System
- Name
- Steps
- Outcome

## 4. Product Format
- Type (course, program, toolkit)

## 5. Delivery Model
- DIY / DWY / DFY

## 6. Final Product Offer
- Description
- Structure

⸻

PART 2: Offer Ladder Builder

Purpose

Create a structured ecosystem of offers at different price points.

⸻

Core Idea

Capture value at every stage: • low commitment → entry • core transformation → main offer • high value → premium

⸻

Assistant Behavior

1. Define customer journey

Identify: • beginner stage • intermediate stage • advanced stage

⸻

2. Build 3 levels

Entry Offer • low price • fast result • low risk • attracts audience

Examples: • templates • mini-products • low-ticket offers

⸻

Core Offer • main transformation • highest volume • balanced price/value

Examples: • programs • courses • memberships

⸻

Premium Offer • highest value • most support • fastest results

Examples: • DFY service • consulting • high-ticket program

⸻

3. Align offers

Ensure: • each level leads to the next • outcomes connect logically • no overlap or confusion

⸻

4. Optimize positioning

Each offer must: • have a clear purpose • target a specific need • justify its price

⸻

Output Format

# OFFER_LADDER.md

## 1. Customer Journey
- Beginner
- Intermediate
- Advanced

## 2. Entry Offer
- Name
- Price
- Outcome
- Format

## 3. Core Offer
- Name
- Price
- Outcome
- Format

## 4. Premium Offer
- Name
- Price
- Outcome
- Format

## 5. Ladder Flow
- How customers move between offers

⸻

PART 3: Upsell / Downsell Skill

Purpose

Increase revenue per customer.

⸻

Core Idea

A customer who buys once is most likely to buy again.

Maximize: • average order value • lifetime value

⸻

Assistant Behavior

1. Identify purchase moment

Find: • where user buys • what they buy first

⸻

2. Design upsells

Upsell = higher value offer

Types: • upgrade • more support • faster results • DFY version

Examples: • course → program • program → consulting

⸻

3. Design downsells

Downsell = lower barrier offer

Used when: • user hesitates • user declines

Examples: • payment plan • lighter version • smaller product

⸻

4. Align with intent

Ensure: • upsell feels natural • downsell feels helpful, not desperate

⸻

5. Keep it simple

Rules: • 1–2 upsells max • 1 downsell option • clear difference in value

⸻

6. Increase perceived value

Upsells should: • feel like a logical upgrade • reduce effort or time • increase success rate

⸻

Output Format

# REVENUE_FLOW.md

## 1. Entry Point
- First purchase

## 2. Upsell Options

### Upsell 1
- Offer
- Why it fits
- Price

### Upsell 2
- Offer
- Why it fits
- Price

## 3. Downsell Options

### Downsell 1
- Offer
- Why it fits
- Price

## 4. Flow Logic
- When upsell appears
- When downsell appears

## 5. Value Increase Strategy
- How revenue per customer increases

⸻

Decision Rules

Productize when: • work repeats • time is the bottleneck • demand exists

Build ladder when: • audience has different budgets • multiple needs exist • scaling is the goal

Add upsells when: • user already trusts you • higher value can be delivered

Add downsells when: • price blocks purchase • simpler option still provides value

⸻

Style Guidelines • keep structure simple • align with real customer journey •