format: apply repo prettier (3.8.1) to the folded skills tree

963 markdown files reformatted with the repository's pinned prettier so pnpm format:check covers the folded tree like every other repo file. The formatter's embedded-language pass also normalized code fences (TS semicolons, closed HTML tags in examples, lowercased CSS hex colors, one renumbered list that skipped an index). Alphanumeric token deltas vs the fold commit were audited file-by-file; all are formatter-equivalent markup normalizations plus the four sanitized skills.
2026-08-19 14:37:17 -05:00
parent d2eeb64433
commit 1a822493ba
962 changed files with 29594 additions and 27188 deletions
@@ -16,22 +16,26 @@ If `.mosaic/product-marketing-context.md` exists, read it before asking question
 Gather this context (ask if not provided):

 ### 1. Business Context
+
 - What type of product? (SaaS, marketplace, e-commerce, service)
 - What's your current pricing (if any)?
 - What's your target market? (SMB, mid-market, enterprise)
 - What's your go-to-market motion? (self-serve, sales-led, hybrid)

 ### 2. Value & Competition
+
 - What's the primary value you deliver?
 - What alternatives do customers consider?
 - How do competitors price?

 ### 3. Current Performance
+
 - What's your current conversion rate?
 - What's your ARPU and churn rate?
 - Any feedback on pricing from customers/prospects?

 ### 4. Goals
+
 - Optimizing for growth, revenue, or profitability?
 - Moving upmarket or expanding downmarket?

@@ -42,14 +46,17 @@ Gather this context (ask if not provided):
 ### The Three Pricing Axes

 **1. Packaging** — What's included at each tier?
+
 - Features, limits, support level
 - How tiers differ from each other

 **2. Pricing Metric** — What do you charge for?
+
 - Per user, per usage, flat fee
 - How price scales with value

 **3. Price Point** — How much do you charge?
+
 - The actual dollar amounts
 - Perceived value vs. cost

@@ -73,6 +80,7 @@ Price should be based on value delivered, not cost to serve:
 The value metric is what you charge for—it should scale with the value customers receive.

 **Good value metrics:**
+
 - Align price with value delivered
 - Are easy to understand
 - Scale as customer grows
@@ -80,18 +88,19 @@ The value metric is what you charge for—it should scale with the value custome

 ### Common Value Metrics

-| Metric | Best For | Example |
-|--------|----------|---------|
-| Per user/seat | Collaboration tools | Slack, Notion |
-| Per usage | Variable consumption | AWS, Twilio |
-| Per feature | Modular products | HubSpot add-ons |
-| Per contact/record | CRM, email tools | Mailchimp |
-| Per transaction | Payments, marketplaces | Stripe |
-| Flat fee | Simple products | Basecamp |
+| Metric             | Best For               | Example         |
+| ------------------ | ---------------------- | --------------- |
+| Per user/seat      | Collaboration tools    | Slack, Notion   |
+| Per usage          | Variable consumption   | AWS, Twilio     |
+| Per feature        | Modular products       | HubSpot add-ons |
+| Per contact/record | CRM, email tools       | Mailchimp       |
+| Per transaction    | Payments, marketplaces | Stripe          |
+| Flat fee           | Simple products        | Basecamp        |

 ### Choosing Your Value Metric

 Ask: "As a customer uses more of [metric], do they get more value?"
+
 - If yes → good value metric
 - If no → price doesn't align with value

@@ -121,6 +130,7 @@ Ask: "As a customer uses more of [metric], do they get more value?"
 ### Van Westendorp Method

 Four questions that identify acceptable price range:
+
 1. Too expensive (wouldn't consider)
 2. Too cheap (question quality)
 3. Expensive but might consider
@@ -131,6 +141,7 @@ Analyze intersections to find optimal pricing zone.
 ### MaxDiff Analysis

 Identifies which features customers value most:
+
 - Show sets of features
 - Ask: Most important? Least important?
 - Results inform tier packaging
@@ -144,16 +155,19 @@ Identifies which features customers value most:
 ### Signs It's Time

 **Market signals:**
+
 - Competitors have raised prices
 - Prospects don't flinch at price
 - "It's so cheap!" feedback

 **Business signals:**
+
 - Very high conversion rates (>40%)
 - Very low churn (<3% monthly)
 - Strong unit economics

 **Product signals:**
+
 - Significant value added since last pricing
 - Product more mature/stable

@@ -169,12 +183,14 @@ Identifies which features customers value most:
 ## Pricing Page Best Practices

 ### Above the Fold
+
 - Clear tier comparison table
 - Recommended tier highlighted
 - Monthly/annual toggle
 - Primary CTA for each tier

 ### Common Elements
+
 - Feature comparison table
 - Who each tier is for
 - FAQ section
@@ -183,6 +199,7 @@ Identifies which features customers value most:
 - Customer logos/trust signals

 ### Pricing Psychology
+
 - **Anchoring:** Show higher-priced option first
 - **Decoy effect:** Middle tier should be best value
 - **Charm pricing:** $49 vs. $50 (for value-focused)
@@ -193,6 +210,7 @@ Identifies which features customers value most:
 ## Pricing Checklist

 ### Before Setting Prices
+
 - [ ] Defined target customer personas
 - [ ] Researched competitor pricing
 - [ ] Identified your value metric
@@ -200,6 +218,7 @@ Identifies which features customers value most:
 - [ ] Mapped features to tiers

 ### Pricing Structure
+
 - [ ] Chosen number of tiers
 - [ ] Differentiated tiers clearly
 - [ ] Set price points based on research
@@ -7,6 +7,7 @@ The Van Westendorp survey identifies the acceptable price range for your product
 ### The Four Questions

 Ask each respondent:
+
 1. "At what price would you consider [product] to be so expensive that you would not consider buying it?" (Too expensive)
 2. "At what price would you consider [product] to be priced so low that you would question its quality?" (Too cheap)
 3. "At what price would you consider [product] to be starting to get expensive, but you still might consider it?" (Expensive/high side)
@@ -25,6 +26,7 @@ Ask each respondent:
 **Optimal pricing zone:** Between OPP and IDP

 ### Survey Tips
+
 - Need 100-300 respondents for reliable data
 - Segment by persona (different willingness to pay)
 - Use realistic product descriptions
@@ -75,18 +77,19 @@ Which feature is LEAST important to you?
 ### Analyzing Results

 Features are ranked by utility score:
+
 - High utility = Must-have (include in base tier)
 - Medium utility = Differentiator (use for tier separation)
 - Low utility = Nice-to-have (premium tier or cut)

 ### Using MaxDiff for Packaging

-| Utility Score | Packaging Decision |
-|---------------|-------------------|
-| Top 20% | Include in all tiers (table stakes) |
-| 20-50% | Use to differentiate tiers |
-| 50-80% | Higher tiers only |
-| Bottom 20% | Consider cutting or premium add-on |
+| Utility Score | Packaging Decision                  |
+| ------------- | ----------------------------------- |
+| Top 20%       | Include in all tiers (table stakes) |
+| 20-50%        | Use to differentiate tiers          |
+| 50-80%        | Higher tiers only                   |
+| Bottom 20%    | Consider cutting or premium add-on  |

 ---

@@ -109,17 +112,21 @@ Statistical analysis reveals price sensitivity per feature
 ## Usage-Value Correlation Analysis

 ### 1. Instrument usage data
+
 Track how customers use your product:
+
 - Feature usage frequency
 - Volume metrics (users, records, API calls)
 - Outcome metrics (revenue generated, time saved)

 ### 2. Correlate with customer success
+
 - Which usage patterns predict retention?
 - Which usage patterns predict expansion?
 - Which customers pay the most, and why?

 ### 3. Identify value thresholds
+
 - At what usage level do customers "get it"?
 - At what usage level do they expand?
 - At what usage level should price increase?
@@ -3,15 +3,18 @@
 ## How Many Tiers?

 **2 tiers:** Simple, clear choice
+
 - Works for: Clear SMB vs. Enterprise split
 - Risk: May leave money on table

 **3 tiers:** Industry standard
+
 - Good tier = Entry point
 - Better tier = Recommended (anchor to best)
 - Best tier = High-value customers

 **4+ tiers:** More granularity
+
 - Works for: Wide range of customer sizes
 - Risk: Decision paralysis, complexity

@@ -20,18 +23,21 @@
 ## Good-Better-Best Framework

 **Good tier (Entry):**
+
 - Purpose: Remove barriers to entry
 - Includes: Core features, limited usage
 - Price: Low, accessible
 - Target: Small teams, try before you buy

 **Better tier (Recommended):**
+
 - Purpose: Where most customers land
 - Includes: Full features, reasonable limits
 - Price: Your "anchor" price
 - Target: Growing teams, serious users

 **Best tier (Premium):**
+
 - Purpose: Capture high-value customers
 - Includes: Everything, advanced features, higher limits
 - Price: Premium (often 2-3x "Better")
@@ -42,20 +48,24 @@
 ## Tier Differentiation Strategies

 **Feature gating:**
+
 - Basic features in all tiers
 - Advanced features in higher tiers
 - Works when features have clear value differences

 **Usage limits:**
+
 - Same features, different limits
 - More users, storage, API calls at higher tiers
 - Works when value scales with usage

 **Support level:**
+
 - Email support → Priority support → Dedicated success
 - Works for products with implementation complexity

 **Access and customization:**
+
 - API access, SSO, custom branding
 - Works for enterprise differentiation

@@ -87,12 +97,14 @@
 ### Identifying Pricing Personas

 Different customers have different:
+
 - Willingness to pay
 - Feature needs
 - Buying processes
 - Value perception

 **Segment by:**
+
 - Company size (solopreneur → SMB → enterprise)
 - Use case (marketing vs. sales vs. support)
 - Sophistication (beginner → power user)
@@ -102,26 +114,27 @@ Different customers have different:

 **Step 1: Define personas**

-| Persona | Size | Needs | WTP | Example |
-|---------|------|-------|-----|---------|
-| Freelancer | 1 person | Basic features | Low | $19/mo |
-| Small Team | 2-10 | Collaboration | Medium | $49/mo |
-| Growing Co | 10-50 | Scale, integrations | Higher | $149/mo |
-| Enterprise | 50+ | Security, support | High | Custom |
+| Persona    | Size     | Needs               | WTP    | Example |
+| ---------- | -------- | ------------------- | ------ | ------- |
+| Freelancer | 1 person | Basic features      | Low    | $19/mo  |
+| Small Team | 2-10     | Collaboration       | Medium | $49/mo  |
+| Growing Co | 10-50    | Scale, integrations | Higher | $149/mo |
+| Enterprise | 50+      | Security, support   | High   | Custom  |

 **Step 2: Map features to personas**

-| Feature | Freelancer | Small Team | Growing | Enterprise |
-|---------|------------|------------|---------|------------|
-| Core features | ✓ | ✓ | ✓ | ✓ |
-| Collaboration | — | ✓ | ✓ | ✓ |
-| Integrations | — | Limited | Full | Full |
-| API access | — | — | ✓ | ✓ |
-| SSO/SAML | — | — | — | ✓ |
-| Audit logs | — | — | — | ✓ |
-| Custom contract | — | — | — | ✓ |
+| Feature         | Freelancer | Small Team | Growing | Enterprise |
+| --------------- | ---------- | ---------- | ------- | ---------- |
+| Core features   | ✓          | ✓          | ✓       | ✓          |
+| Collaboration   | —          | ✓          | ✓       | ✓          |
+| Integrations    | —          | Limited    | Full    | Full       |
+| API access      | —          | —          | ✓       | ✓          |
+| SSO/SAML        | —          | —          | —       | ✓          |
+| Audit logs      | —          | —          | —       | ✓          |
+| Custom contract | —          | —          | —       | ✓          |

 **Step 3: Price to value for each persona**
+
 - Research willingness to pay per segment
 - Set prices that capture value without blocking adoption
 - Consider segment-specific landing pages
@@ -133,6 +146,7 @@ Different customers have different:
 ### When to Use Freemium

 **Freemium works when:**
+
 - Product has viral/network effects
 - Free users provide value (content, data, referrals)
 - Large market where % conversion drives volume
@@ -140,6 +154,7 @@ Different customers have different:
 - Clear feature/usage limits for upgrade trigger

 **Freemium risks:**
+
 - Free users may never convert
 - Devalues product perception
 - Support costs for non-paying users
@@ -148,6 +163,7 @@ Different customers have different:
 ### When to Use Free Trial

 **Free trial works when:**
+
 - Product needs time to demonstrate value
 - Onboarding/setup investment required
 - B2B with buying committees
@@ -155,6 +171,7 @@ Different customers have different:
 - Product is "sticky" once configured

 **Trial best practices:**
+
 - 7-14 days for simple products
 - 14-30 days for complex products
 - Full access (not feature-limited)
@@ -162,6 +179,7 @@ Different customers have different:
 - Credit card optional vs. required trade-off

 **Credit card upfront:**
+
 - Higher trial-to-paid conversion (40-50% vs. 15-25%)
 - Lower trial volume
 - Better qualified leads
@@ -169,11 +187,13 @@ Different customers have different:
 ### Hybrid Approaches

 **Freemium + Trial:**
+
 - Free tier with limited features
 - Trial of premium features
 - Example: Zoom (free 40-min, trial of Pro)

 **Reverse trial:**
+
 - Start with full access
 - After trial, downgrade to free tier
 - Example: See premium value, live with limitations until ready
@@ -185,6 +205,7 @@ Different customers have different:
 ### When to Add Custom Pricing

 Add "Contact Sales" when:
+
 - Deal sizes exceed $10k+ ARR
 - Customers need custom contracts
 - Implementation/onboarding required
@@ -194,6 +215,7 @@ Add "Contact Sales" when:
 ### Enterprise Tier Elements

 **Table stakes:**
+
 - SSO/SAML
 - Audit logs
 - Admin controls
@@ -201,6 +223,7 @@ Add "Contact Sales" when:
 - Security certifications

 **Value-adds:**
+
 - Dedicated support/success
 - Custom onboarding
 - Training sessions
@@ -210,14 +233,17 @@ Add "Contact Sales" when:
 ### Enterprise Pricing Strategies

 **Per-seat at scale:**
+
 - Volume discounts for large teams
 - Example: $15/user (standard) → $10/user (100+)

 **Platform fee + usage:**
+
 - Base fee for access
 - Usage-based above thresholds
 - Example: $500/mo base + $0.01 per API call

 **Value-based contracts:**
+
 - Price tied to customer's revenue/outcomes
 - Example: % of transactions, revenue share