Skip to main content

value-accelerator

Reduce the time to first meaningful result to increase conversions and decrease drop-off. Use when the offer feels slow, results feel far away, or users drop off after buying. Maps friction, defines a quick-win asset, redesigns onboarding, and improves perceived speed — outputs TIME_TO_VALUE.md.

インストールへ移動

ソース情報

リポジトリ
alexsmedile/hormozi-skills
ソースの最終更新活動
2026年4月14日 21:59
検出された SKILL.md の言語
英語
スター
174
フォーク
33

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md を表示中

SKILL.md
ソースの指示 · 読み取り専用プレビュー
name
value-accelerator
description
Reduce the time to first meaningful result to increase conversions and decrease drop-off. Use when the offer feels slow, results feel far away, or users drop off after buying. Maps friction, defines a quick-win asset, redesigns onboarding, and improves perceived speed — outputs TIME_TO_VALUE.md.
# Skill: Time-to-Value Accelerator ## Purpose Reduce the time it takes for a customer to experience their **first meaningful result**. This skill increases conversions by: - shortening time delay - increasing perceived speed - creating early wins - making the offer feel fast and actionable It directly improves this part of the value equation: Time Delay ↓ → Value ↑ --- ## When to Use Activate this skill when: - the offer feels slow or overwhelming - customers delay buying because results feel far away - conversions are low despite a strong outcome - users drop off after buying - the offer requires too much setup before value --- ## Inputs This skill can work with: - an `OFFER.md` - a rough offer description - a product or service idea - a course, template, or program - a funnel or onboarding flow --- ## Core Outcome The assistant produces: - a faster path to first result - a “quick win” mechanism - a redesigned onboarding experience - reduced friction in execution - a clearer perception of speed - updated offer structure with faster value delivery --- ## Assistant Behavior ### 1. Identify the current time-to-value Extract: - what result the offer promises - how long it currently takes to achieve - when the user sees the first win - what happens immediately after purchase Then summarize: > Right now, the first real result happens after X. > This feels slow because the user must first do Y and Z. --- ### 2. Find friction points Break down the journey from purchase → result. Look for: - delays before starting - setup complexity - too many steps - unclear instructions - cognitive overload - missing guidance Map it like: Step → Friction → Delay caused --- ### 3. Define the “First Win” The first win should be: - fast (minutes or hours, not weeks) - visible (clear result) - meaningful (feels like progress) - motivating (builds momentum) Ask or decide: - What is the smallest useful result? - What can they achieve in the first 5–30 minutes? - What would make them say “this works”? --- ### 4. Design a Quick Win Asset Create a specific asset that delivers the first win fast. Possible formats: - checklist - template - swipe file - mini-tool - guided action - audit - script - automation - pre-built system Output: - asset name - what it does - how fast it works - what result it gives Example: - “30-Minute Client Outreach Script” - “Plug-and-Play Notion Dashboard” - “First Sale Setup Template” --- ### 5. Restructure Onboarding Design the first 24 hours after purchase. Goal: eliminate hesitation and start action immediately. Include: - welcome message - clear first step - quick win asset - simple instructions - expected outcome Output a step-by-step flow: Hour 0 → what they see Hour 1 → what they do Day 1 → what they achieve --- ### 6. Reduce Time Delay Suggest ways to compress time: - pre-fill work (done-for-you elements) - remove unnecessary steps - batch actions - simplify decisions - give exact instructions - provide examples - create shortcuts --- ### 7. Reduce Effort & Sacrifice Make the process feel easier. Suggest: - automation - templates instead of blank pages - guided workflows - fewer choices - default paths - optional shortcuts --- ### 8. Improve Perceived Speed Even if real time doesn’t change, perception can. Techniques: - name the time frame clearly (“in 30 minutes”, “in 1 day”) - highlight quick wins in the pitch - show early results first - break big outcomes into milestones - emphasize “start fast” messaging --- ### 9. Upgrade the Offer Structure Integrate changes into the offer: - add quick win as first component - move fast results earlier - reorder modules or steps - highlight speed in core promise - adjust bonuses to support speed --- ## Output Format ```md # TIME_TO_VALUE.md ## 1. Current Time-to-Value - Promised result - Time to full result - Time to first win - Key delays ## 2. Friction Map - Step → Friction → Delay ## 3. First Win Definition - What the first win is - Why it matters - When it happens ## 4. Quick Win Asset - Name - Format - What it does - Time to result ## 5. Onboarding Flow - Hour 0 - Hour 1 - Day 1 ## 6. Time Reduction Ideas - What to remove - What to simplify - What to pre-build ## 7. Effort Reduction Ideas - Automation - Templates - Shortcuts ## 8. Perceived Speed Improvements - Messaging changes - Structure changes ## 9. Updated Offer Structure - New flow - First result placement - Key upgrades ``` ⸻ Decision Rules Create a faster first win when: • the first result takes more than a day • users feel overwhelmed at the start • drop-off happens early Add a quick win asset when: • the offer starts with theory • users must “figure things out” • the first step feels unclear Simplify when: • there are too many steps • instructions are vague • users need to make too many decisions Reorder when: • high-value outcomes come too late • motivation drops early ⸻ Examples Before • Buy course • Watch 5 modules • Then take action • Result in 2–3 weeks After • Buy course • Use “Day 1 Quick Start Template” • Get first result in 30 minutes • Continue with deeper modules ⸻ Style Guidelines • focus on speed and clarity • avoid complexity • favor action over theory • prioritize early wins • remove unnecessary steps ⸻ Success Criteria The skill works when: • the user gets a result fast • the first action feels easy • momentum builds quickly • the offer feels “fast” to buy • drop-off decreases • perceived value increases
GitHubで見る