Marketing Foundation
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.
Understand customer needs, compare competitors and plan a community around real member value.
Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.
Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.
Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.
Turn repeatable service work into defined packages, an offer ladder and optional upgrade paths. Use Offer Delivery Design when only the fulfillment format is undecided.
--- 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 ```md # 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 ```md # 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 ```md # 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 • prioritize clarity over complexity • focus on value at each step ⸻ Success Criteria The skill works when: • services become scalable • offers are clearly structured • customers have multiple entry points • revenue per customer increases • business scales beyond time constraints
Turn repeatable service work into defined packages, an offer ladder and optional upgrade paths. Use Offer Delivery Design when only the fulfillment format is undecided.
The structured plan or review specified in the original, with evidence and open questions.
Confirm task inputs, follow the source workflow and apply the explicit M11 qualifications below.
Current service workflow, customer needs, support effort, costs and existing offers.
Recurring and repeat-purchase revenue is a hypothesis until supported by demand and retention evidence. Premium does not inherently mean fastest or best. Preserve accessibility and cancellation choices; optional upgrades must be explicit and genuinely useful. Check margins, capacity and support before suggesting prices or scale.
Use Service Productization for [BUSINESS/TASK]. Ask for missing inputs: Current service workflow, customer needs, support effort, costs and existing offers. Return the source output format and label evidence, assumptions and validation steps. Recurring and repeat-purchase revenue is a hypothesis until supported by demand and retention evidence. Premium does not inherently mean fastest or best. Preserve accessibility and cancellation choices; optional upgrades must be explicit and genuinely useful. Check margins, capacity and support before suggesting prices or scale.
Automatic upselling, hidden recurring charges or assuming standardization removes delivery costs.
M11 added task routing, German terms, scope and evidence requirements while preserving original authorship. Recurring and repeat-purchase revenue is a hypothesis until supported by demand and retention evidence. Premium does not inherently mean fastest or best. Preserve accessibility and cancellation choices; optional upgrades must be explicit and genuinely useful. Check margins, capacity and support before suggesting prices or scale.
MIT License Copyright (c) 2026 Alessandro Smedile Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copy the text below, then paste it into your chat.