SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsdfy-dwy-diy

dfy-dwy-diy

General & other

View repository

Updated 10-15 16:47

About this skill

Skill: Delivery Mechanism Designer (DFY vs DWY vs DIY)

Purpose

Choose the best way to deliver the result.

This skill decides how the value is delivered, not just what is delivered.

It optimizes for:

  • speed (how fast results happen)
  • ease (how hard it feels)
  • perceived value (what it’s worth in the buyer’s mind)

A weak delivery kills a strong idea.
A strong delivery can make a simple idea sell.

When to Use

Activate this skill when:

  • the offer exists but feels weak
  • conversions are low despite a good outcome
  • delivery format is unclear
  • the result requires too much effort
  • the user is unsure between product, service, or hybrid
  • scaling vs customization is a tradeoff

Inputs

This skill works with:

  • an OFFER.md
  • a rough offer idea
  • a product or service description
  • a target outcome + audience
  • an existing delivery format

Core Outcome

The assistant produces:

  • the best delivery model (DFY, DWY, DIY)
  • reasoning behind the choice
  • tradeoffs explained
  • hybrid delivery ideas
  • upgraded delivery structure

Key Models

DIY (Do It Yourself)

User does everything.

Examples

  • course
  • ebook
  • template
  • toolkit

Pros

  • scalable
  • low cost to deliver
  • high margins

Cons

  • low perceived value
  • low completion rates
  • requires discipline

DWY (Done With You)

You guide the user.

Examples

  • coaching
  • cohort program
  • group calls
  • feedback loops

Pros

  • higher success rate
  • higher perceived value
  • builds trust

Cons

  • less scalable
  • requires time
  • depends on user effort

DFY (Done For You)

You do the work.

Examples

  • agency
  • service
  • setup
  • implementation

Pros

  • highest perceived value
  • fastest results
  • lowest effort for customer

Cons

  • low scalability
  • higher delivery cost
  • operational complexity

Assistant Behavior

1. Understand the outcome

Extract:

  • what result is promised
  • how complex it is
  • how fast it needs to happen
  • what skills are required

Then summarize:

The result requires X level of effort and Y level of skill.
Speed expectations are Z.

2. Analyze the customer

Identify:

  • skill level
  • available time
  • willingness to learn
  • willingness to pay
  • urgency of the problem

Example:

This customer wants results fast and does not want to learn deeply.

3. Evaluate each delivery model

Score DIY, DWY, DFY based on:

Speed

  • how fast results happen

Ease

  • how much work the user does

Perceived Value

  • how valuable it feels

Scalability

  • how easy it is to grow

4. Recommend the best model

Choose:

  • primary model (DFY, DWY, or DIY)
  • explain why it fits best

Example:

DFY fits best because the customer wants speed and has low tolerance for effort.

5. Identify gaps in the current model

If a model already exists, evaluate:

  • is it too heavy?
  • is it too light?
  • does it mismatch the outcome?
  • does it require too much effort?
  • does it slow results?

6. Propose hybrid models

Combine formats to improve value.

Common hybrids:

  • DIY + template + checklist
  • DIY + audit
  • DIY + async support
  • DWY + templates + group calls
  • DFY + light coaching
  • DFY + dashboard + reporting

Output:

  • 2–4 hybrid options
  • what each includes
  • why it improves the offer

7. Optimize for speed

Suggest ways to:

  • move toward DFY elements
  • pre-build parts
  • reduce setup time
  • deliver partial results faster

8. Optimize for ease

Suggest:

  • more guidance
  • fewer steps
  • better structure
  • simpler execution

9. Optimize for perceived value

Increase value without adding cost:

  • add DFY components
  • include expert involvement
  • add audits or feedback
  • show transformation clearly

10. Suggest upgrade paths

Design progression:

  • DIY → DWY → DFY
  • low-ticket → mid-ticket → premium

This creates:

  • entry point
  • core offer
  • premium tier

Output Format

# DELIVERY_MECHANISM.md

## 1. Outcome Analysis
- Desired result
- Complexity
- Speed required
- Skills required

## 2. Customer Profile
- Skill level
- Time availability
- Urgency
- Willingness to pay

## 3. Delivery Model Comparison

### DIY
- Score (speed, ease, value)
- Pros
- Cons

### DWY
- Score
- Pros
- Cons

### DFY
- Score
- Pros
- Cons

## 4. Recommended Model
- Primary model
- Reasoning

## 5. Current Model Gaps
- What’s weak
- What’s missing

## 6. Hybrid Options
- Option 1
- Option 2
- Option 3

## 7. Speed Improvements
- Suggestions

## 8. Ease Improvements
- Suggestions

## 9. Value Perception Upgrades
- Suggestions

## 10. Offer Ladder
- Entry offer
- Core offer
- Premium offer

⸻

Decision Rules

Choose DIY when: • the problem is simple • the user enjoys learning • price must be low • scalability is the goal

Choose DWY when: • guidance improves success • accountability matters • medium price point is acceptable

Choose DFY when: • speed is critical • the task is complex • the user lacks skill or time • willingness to pay is high

⸻

Hybrid Rules

Use hybrid when: • DIY alone feels too weak • DFY alone is too expensive • users need both speed and guidance

⸻

Examples

Weak • course with no support

Improved • course + templates + audit

⸻

Weak • consulting only

Improved • consulting + DFY setup + dashboard

⸻

Style Guidelines • focus on delivery, not theory • prioritize speed and ease • match format to customer reality • reduce effort where possible • increase value perception smartly

⸻

Success Criteria

The skill works when: • the delivery matches the outcome • the user sees results faster • effort feels lower • perceived value increases • the offer becomes easier to sell