---
name: productize-yourself-blueprint
description: Design a complete "productize yourself" blueprint to convert expertise into a scalable product system. Use when someone wants to turn their knowledge, service, or time-based work into a product that sells without their live presence. Triggers on phrases like "productize myself", "turn expertise into product", "productize your knowledge", "scalable product system", "product ladder", "digital product from expertise", "Alex Hormozi productize", "Dan Koe product", "expertise to product", "build a machine not a job", or when someone describes what they do for clients and wants to stop trading time for money.
---

# Productize Yourself Blueprint

A framework for converting knowledge workers into scalable operators. Inspired by Naval Ravikant, Dan Koe, and Alex Hormozi — expertise becomes a machine, not more client work.

## Core Principle

A productized service or digital product is one that:
- Delivers a **named transformation** (not information)
- Runs **without your live presence**
- Has a **proprietary mechanism** (framework, system, or method)
- Scales through **code or media leverage**

**If it requires you to be live to deliver, it's not a product — it's a service. Reject it.**

## Blueprint Process

### Step 1: Define the Core Transformation

Identify the single most valuable transformation the user can deliver. Ask:
- What do people **become** after working with you?
- What problem do you solve that they would pay to avoid?
- What outcome do you deliver consistently?

Distill into one sentence: *"I help [WHO] go from [BEFORE STATE] to [AFTER STATE] in [TIMEFRAME] without [PAIN POINT]."*

### Step 2: Map the Product Ladder

Design a free-to-premium stack. Each rung must require **zero live presence** at the point of delivery:

| Tier | Purpose | Example Formats |
|------|---------|-----------------|
| **Free** — Trust & discovery | Lead magnet, newsletter, social content, mini-tool | Checklist, calculator, 5-minute audit, PDF guide |
| **Low** — First transaction | Digital product under 100 | Template, playbook, mini-course, Notion system, prompt pack |
| **Mid** — Core revenue | Productized service or course £200–£1,000 | Self-paced course with proprietary framework, cohort-based async course, tool/software |
| **High** — Premium outcomes | High-ticket product 1,000+ | Licensed methodology, white-label system, community + curriculum, software |

Rules:
- Every tier must have a **named proprietary mechanism** (e.g., "The 3-Stack Audit," "The Specific Knowledge Excavator")
- No generic courses. Must include a framework, system, or methodology that is uniquely yours.
- Delivery must be async or automated — no live calls, no 1:1 delivery at scale.

### Step 3: Design the 30-Day Conversion

Pick the **time-based service** the user currently sells. Convert it into a product within 30 days.

**Conversion formula:**
- **Live delivery** → **Recorded or templated delivery**
- **Custom work** → **Standardized framework with select customization points**
- **1:1 feedback** → **Self-assessment rubric or peer review system**
- **Ongoing retainer** → **One-time purchase with optional upgrade path**

Output:
- What the live service currently is
- What the product version becomes
- What gets recorded, templated, or systematized
- The exact build tasks for 30 days

### Step 4: Design the Winning Product

Define the flagship product in detail:

**Name:** `[Product Name] + [Proprietary Mechanism]`

**Contents:** What's inside — modules, templates, tools, frameworks, bonuses

**Delivery Mechanism:** How it reaches buyers without the user's presence
- Platform (Gumroad, Teachable, Notion, Stripe, etc.)
- Delivery format (async course, Notion template, downloadable toolkit, SaaS)
- Automation layer (email sequences, onboarding flows, access grants)

**Irreplaceability Factor:** What makes this product impossible to replicate by a competitor with generic knowledge
- Proprietary framework
- Unique combination of the user's specific knowledge
- Embedded methodology derived from lived experience

**Price Point:** Recommended price + rationale based on transformation value, not content volume

### Step 5: Match Distribution to Existing Platform

**Critical rule:** Do NOT suggest starting from zero on a new channel. Map distribution to where the user already has traction or natural fit.

| If their platform is... | Distribution strategy |
|------------------------|----------------------|
| LinkedIn | Newsletter → carousel → lead magnet → product |
| Twitter/X | Thread → viral hook → landing page → product |
| YouTube | Video → description link → free tool → paid product |
| Newsletter/Email | Direct pitch → product ladder within existing list |
| Podcast | Show notes → free resource → product mention |
| No audience | Borrowed distribution — guest posts, collaborations, SEO |

### Step 6: Write the Positioning Statement

One sentence that can be used as a headline, bio, or launch post:

Format: *"[Product Name] is a [format] that helps [WHO] achieve [TRANSFORMATION] using [PROPRIETARY MECHANISM] — without [PAIN POINT OF OLD WAY]."*

## Output Format

```
## Your Core Transformation

[I help WHO go from BEFORE STATE to AFTER STATE in TIMEFRAME without PAIN POINT.]

## Product Ladder

| Tier | Product Name | Format | Price | Delivery |
|------|-------------|--------|-------|----------|
| Free | [Name] | [Format] | Free | [How delivered] |
| Low | [Name] | [Format] | £X | [How delivered] |
| Mid | [Name] | [Format] | £X | [How delivered] |
| High | [Name] | [Format] | £X | [How delivered] |

## 30-Day Conversion Plan

**Current service:** [What they do live]
**Product version:** [What it becomes]
**What gets systematized:** [Recorded / templated / automated]

### Build Tasks (30 days)
1. [Task — Week 1]
2. [Task — Week 2]
3. [Task — Week 3]
4. [Task — Week 4]

## Winning Product Structure

**Name:** [Product Name + Proprietary Mechanism]

**Contents:**
- [Module / component 1]
- [Module / component 2]
- [Module / component 3]
- [Bonus / tool / template]

**Delivery:** [Platform + format + automation]

**Irreplaceability:** [Why a competitor can't copy this]

**Price:** [X] — [Rationale]

## Distribution Channel

**Platform:** [Where they already are]
**Strategy:** [Specific funnel from content to product]

## Launch Positioning Statement

[One sentence — headline-ready]

## Week 1 Build Roadmap

1. [Concrete task — Day 1-2]
2. [Concrete task — Day 3-4]
3. [Concrete task — Day 5-7]
```

## Guardrails

- **Reject live-dependent products.** If it requires the user's presence to deliver, redesign it.
- **Every product must have a named mechanism.** Generic titles like "SEO Course" are banned. "The Keyword Gap System" is acceptable.
- **Distribution must match existing platform.** Never recommend building on a platform from zero unless the user has no audience at all.
- **Price by transformation, not volume.** A 20-page playbook that solves a 10K problem can cost £500. A 20-hour course that solves a £50 problem should cost £20.
- **The 30-day plan must be buildable.** Not aspirational. Actual tasks with actual tools.
