@rubytech/create-maxy-code 0.1.167 → 0.1.170

package/payload/platform/plugins/venture-studio/skills/zero-to-prototype/references/innovation-accounting.md

@@ -1,290 +0,0 @@
-# Innovation Accounting
-
-## Purpose
-Measure progress toward product-market fit when traditional metrics (revenue, profit) don't yet apply, providing a framework for accountability and decision-making in early-stage ventures.
-
-## When to Use
-- Early stage when revenue is minimal or zero
-- When traditional metrics don't reflect progress
-- Need to demonstrate progress to stakeholders (board, investors)
-- Making pivot or persevere decisions
-- Setting milestones for innovation teams
-
-## Process
-
-### 1. The Three Steps of Innovation Accounting
-
-**Step 1: Establish Baseline**
-Use an MVP or experiment to measure where you are NOW
-- Run your first experiment
-- Measure current conversion rates, engagement, etc.
-- Establish starting point for all key metrics
-
-**Step 2: Tune the Engine**
-Make changes to improve metrics toward your ideal
-- Each experiment targets specific metric improvement
-- If changes don't improve metrics, they failed
-- Iterate until metrics approach target
-
-**Step 3: Pivot or Persevere**
-Decide whether progress justifies continuing
-- Are metrics improving toward sustainable business?
-- If yes: continue tuning
-- If no: pivot (structured change) or stop
-
-### 2. Define Your Learning Milestones
-
-Instead of revenue targets (too early), define learning milestones:
-
-**Problem Validation Milestones:**
-- [ ] Completed 20+ customer discovery conversations
-- [ ] Identified 5+ earlyvangelists with all characteristics
-- [ ] Documented problem in customer's own words
-- [ ] Quantified cost of problem (time, money, pain)
-
-**Solution Validation Milestones:**
-- [ ] Built MVP that tests value hypothesis
-- [ ] Achieved X% activation rate
-- [ ] Received commitment (time, money, reputation)
-- [ ] Got referrals to additional potential customers
-
-**Product-Market Fit Milestones:**
-- [ ] Achieved Y% retention at Week 4
-- [ ] Paying customers without heavy sales effort
-- [ ] Word-of-mouth driving new customers
-- [ ] 40%+ "very disappointed" on Sean Ellis test
-
-**Growth Milestones:**
-- [ ] Identified primary engine of growth
-- [ ] Achieved positive unit economics (LTV > CAC)
-- [ ] Demonstrated repeatable acquisition channel
-- [ ] Scaling while maintaining quality
-
-### 3. Track Actionable Metrics
-
-**Vanity metrics to avoid:**
-- Total registered users (if most are inactive)
-- Page views (if they don't convert)
-- "Engagement" without definition
-- Gross numbers without cohort analysis
-
-**Actionable metrics to track:**
-- Activation rate (% reaching "aha moment")
-- Retention by cohort (are newer cohorts better?)
-- Conversion rate (% taking desired action)
-- Engagement frequency (DAU/MAU ratio)
-- Net Promoter Score (would they recommend?)
-
-**The Three A's of Good Metrics:**
-
-1. **Actionable:** Clear cause and effect
-   - Bad: "Engagement increased"
-   - Good: "Changing onboarding increased activation 20%"
-
-2. **Accessible:** Everyone understands
-   - Use real units (customers, dollars)
-   - Make dashboards simple
-
-3. **Auditable:** Can be verified
-   - Can you manually check?
-   - Can you talk to the people in the data?
-
-### 4. Build Your Innovation Dashboard
-
-Track these categories:
-
-**Validated Learning:**
-- Hypotheses tested this period
-- Hypotheses validated vs. invalidated
-- Key insights documented
-
-**Progress Metrics:**
-- Activation rate (current vs. target)
-- Retention cohorts (current vs. target)
-- Conversion rate (current vs. target)
-- Growth rate (current vs. target)
-
-**Engine-Specific Metrics:**
-- Sticky: Churn rate, DAU/MAU
-- Viral: K-factor, cycle time
-- Paid: CAC, LTV, LTV:CAC ratio
-
-**Resource Efficiency:**
-- Burn rate
-- Runway remaining
-- Cost per experiment
-- Time per iteration
-
-### 5. Report Progress
-
-For stakeholders, report:
-
-**What we learned:**
-- Hypotheses tested
-- Results (validated/invalidated)
-- Insights that changed our understanding
-
-**Where we are:**
-- Current metrics vs. baseline
-- Trend direction (improving, stable, declining)
-- Distance to target milestones
-
-**What we're doing next:**
-- Next experiments planned
-- Expected timeline
-- What we need to learn
-
-**Decision points ahead:**
-- When we'll have enough data to decide
-- What would trigger a pivot
-- What would trigger scaling
-
-### 6. Make Pivot/Persevere Decisions
-
-**Hold regular decision meetings:**
-- Weekly for early-stage (high iteration rate)
-- Monthly for growth-stage
-- Include product AND business perspectives
-
-**Evaluate evidence:**
-- Are metrics moving in the right direction?
-- Is the rate of improvement sufficient?
-- What would change our trajectory?
-
-**Apply decision criteria:**
-
-| Situation | Evidence | Decision |
-|-----------|----------|----------|
-| Improving fast | Metrics trending toward target | Persevere |
-| Improving slowly | Progress but below expectations | Set deadline for decision |
-| Flat | Multiple experiments, no change | Consider pivot |
-| Declining | Getting worse despite efforts | Pivot or stop |
-
-### 7. Avoid Common Traps
-
-**The success theater trap:**
-- Reporting vanity metrics that look good
-- Fix: Report only actionable metrics
-
-**The "just one more feature" trap:**
-- Believing the next feature will change everything
-- Fix: Set clear experiment criteria upfront
-
-**The prolonged runway trap:**
-- Persevering because you still have money
-- Fix: Time-box decisions regardless of runway
-
-**The "we're learning" trap:**
-- Calling all failure "learning" without action
-- Fix: Document what changed based on learning
-
-### 8. Synthesis
-
-After setting up innovation accounting:
-- What are your current baseline metrics?
-- What would validated product-market fit look like (targets)?
-- What experiments will move you toward targets?
-- When will you make your next pivot/persevere decision?
-- What would trigger a pivot vs. persevering?
-
-## Example
-
-**Startup**: AI-powered customer support tool
-
-### Baseline (Month 0)
-
-After launching MVP:
-- Activation rate: 15% (% completing first ticket deflection)
-- Week 1 retention: 20%
-- Week 4 retention: 8%
-- Willingness to pay: 2% (% attempting purchase)
-
-### Targets (Product-Market Fit)
-
-Based on comparable companies:
-- Activation rate: 50%
-- Week 1 retention: 60%
-- Week 4 retention: 40%
-- Willingness to pay: 10%
-
-### Month 1-3: Tuning the Engine
-
-**Experiments run:**
-
-| Experiment | Target | Result | Learning |
-|------------|--------|--------|----------|
-| Simplified onboarding | Activation 25% | 28% ✓ | Removing optional steps helps |
-| In-app guidance | Activation 35% | 32% ✓ | Guided setup works |
-| Email drip campaign | Retention 25% | 22% ✗ | Users don't read emails |
-| Slack integration | Retention 35% | 38% ✓ | Integration = stickiness |
-| Free trial extension | WTP 5% | 3% ✗ | Longer trial doesn't convert |
-
-**Month 3 metrics:**
-- Activation: 32% (was 15%, target 50%)
-- Week 1 retention: 35% (was 20%, target 60%)
-- Week 4 retention: 18% (was 8%, target 40%)
-- WTP: 4% (was 2%, target 10%)
-
-### Pivot/Persevere Decision (Month 3)
-
-**Evidence:**
-- Activation: +17% improvement (good trajectory)
-- Retention: +15%/+10% improvement (good trajectory)
-- WTP: +2% improvement (slow but positive)
-
-**Decision: Persevere** with focus on:
-- Continue onboarding improvements
-- Double down on integrations (proven driver)
-- Experiment more on conversion to paid
-
-### Month 4-6: Continued Tuning
-
-**Experiments run:**
-
-| Experiment | Target | Result |
-|------------|--------|--------|
-| Integration marketplace | Retention 45% | 48% ✓ |
-| Usage-based pricing | WTP 8% | 7% ~ |
-| Success stories/case studies | WTP 8% | 9% ✓ |
-| Reduced price | WTP 12% | 15% ✓ |
-
-**Month 6 metrics:**
-- Activation: 52% (target 50% ✓ HIT)
-- Week 1 retention: 55% (target 60% ~)
-- Week 4 retention: 38% (target 40% ~)
-- WTP: 15% (target 10% ✓ HIT)
-
-### Pivot/Persevere Decision (Month 6)
-
-**Evidence:**
-- 3 of 4 targets hit or nearly hit
-- Clear trajectory toward product-market fit
-- Unit economics becoming viable
-
-**Decision: Persevere and begin scaling**
-- Transition from finding fit to growth
-- Begin paid acquisition experiments
-- Hire first customer success person
-
-### Innovation Accounting Report (for Board)
-
-**Summary:**
-Over 6 months, we validated:
-1. Problem exists (customers have support overload)
-2. Solution works (AI deflects tickets effectively)
-3. Business model viable (customers will pay at current price)
-
-**Key Metrics:**
-| Metric | Baseline | Month 3 | Month 6 | Target |
-|--------|----------|---------|---------|--------|
-| Activation | 15% | 32% | 52% | 50% |
-| Week 4 Retention | 8% | 18% | 38% | 40% |
-| Conversion | 2% | 4% | 15% | 10% |
-
-**Next Phase:**
-Shift from innovation accounting to growth accounting
-- Focus on CAC, LTV, payback period
-- Begin scaling acquisition
-- Maintain product-market fit while growing
-
-**Insight:** Innovation accounting provided clear evidence of progress when revenue was near-zero. The metrics showed we were building something people wanted, not just something that felt good to build.

package/payload/platform/plugins/venture-studio/skills/zero-to-prototype/references/jtbd.md

@@ -1,105 +0,0 @@
-# Jobs to Be Done (JTBD)
-
-## Purpose
-Understand what customers are truly "hiring" your product to do, revealing the underlying job beyond surface-level features.
-
-## When to Use
-- Validating new business ideas or offers
-- Refining value propositions
-- When you're focused on features instead of outcomes
-- GTM strategy development
-
-## Process
-
-1. **Identify the "job"**
-   - What progress is the customer trying to make?
-   - What situation triggers their need?
-   - "When _____, I want to _____, so I can _____"
-
-2. **Understand the job context**
-   - Functional job: What task are they trying to complete?
-   - Emotional job: How do they want to feel?
-   - Social job: How do they want to be perceived?
-
-3. **Map the current solution**
-   - What are they "hiring" today to do this job?
-   - What are they "firing" by choosing your idea?
-   - What are the switching costs?
-
-4. **Customer interview (10 questions, ranked by importance)**
-
-   Prepare a script of 10 open-ended questions tailored to the idea. Use this template as a starting point, adapting language and specifics to the target customer:
-
-   | # | Question | Why it matters |
-   |---|---------|---------------|
-   | 1 | "Walk me through what happens when [trigger event]." | Opens the floodgates. Reveals the full workflow without leading. Listen for pain, bottlenecks, and workarounds. |
-   | 2 | "What happens when you can't deal with [the job] right away?" | Tests the cost of delay — the core pain. Listen for: missed opportunities, stress, knock-on effects. |
-   | 3 | "How do you currently handle [the job]? What tools, people, or processes?" | Maps current solutions being "hired." Listen for: makeshift tools, people doing it manually, things that don't scale. |
-   | 4 | "Can you tell me about a time when [the job] went wrong or fell through the cracks?" | Concrete stories beat hypotheticals. Listen for: specific examples, what it cost them, how it felt. |
-   | 5 | "Who else is involved in [the job]? Does anyone help you with it?" | Identifies the real buyer vs the real user — they're often different people. Listen for: partners, assistants, colleagues picking up slack. |
-   | 6 | "What's the most time-consuming part of [the job]?" | Pinpoints the highest-value automation target. Listen for: the 20% that takes 80% of the time. |
-   | 7 | "What would you never want something to do on your behalf? What's off limits?" | Tests trust boundaries without asking "would you trust X?" Reveals what they WOULD trust by elimination. |
-   | 8 | "If something could handle [the job] for you — automatically, 24/7 — what would that free you up to do?" | Lets them articulate the value in their own words. Don't mention price yet. Listen for: time, stress, relationships, revenue. |
-   | 9 | "What have you tried before to solve this? What worked, what didn't?" | Reveals failed alternatives and switching triggers. Listen for: tools abandoned, services cancelled, why they stopped. |
-   | 10 | "If this cost about [anchor price] per month, and it meant [core outcome], would that be worth it?" | Last question deliberately. By now they've articulated the pain. Tests willingness to pay against a concrete anchor. Listen for: "definitely", "I'd need to see it", "that's a lot." |
-
-   **Follow-up prompts (use throughout):**
-   - "Tell me more about that..."
-   - "How often does that happen?"
-   - "What did that cost you?"
-   - "Who else is affected by that?"
-
-   **Interview principles:**
-   - One question at a time. Let them talk. Silence is your friend.
-   - Never pitch during the interview. You're learning, not selling.
-   - Record if possible (with permission). Transcripts are gold.
-   - The best insights come from follow-ups, not the scripted questions.
-   - Ask about the PAST (what happened) not the FUTURE (what would you do). Past behaviour predicts future behaviour.
-
-5. **Identify job outcomes**
-   - How do they measure success?
-   - What does "better" look like?
-   - What struggles exist with current solutions?
-
-6. **Uncover competing alternatives**
-   - What else could they hire to do this job?
-   - What's the "non-consumption" alternative (doing nothing)?
-
-7. **Define your job statement**
-   - "Help [customer] [job to be done] [context/constraint] so they can [desired outcome]"
-
-8. **Synthesis**
-   - Is your idea actually hired to do this job?
-   - Are you solving for the right outcome?
-   - What would make you the obvious choice?
-
-## Example
-
-**Idea**: "Online course teaching small business owners to use AI tools"
-
-**Job to be done**: "When I'm overwhelmed by repetitive tasks and limited time, I want to work smarter without hiring more people, so I can grow my business while maintaining work-life balance"
-
-**Job context**:
-- **Functional**: Automate repetitive work, reduce manual tasks
-- **Emotional**: Feel in control, reduce stress, feel innovative
-- **Social**: Be seen as forward-thinking by peers
-
-**Current solutions being "hired"**:
-- Virtual assistants (expensive, management overhead)
-- Doing it themselves (time-consuming, exhausting)
-- Ignoring the work (guilt, falling behind)
-
-**Success metrics**:
-- Hours saved per week
-- Reduced stress/better sleep
-- Revenue maintained or growing
-- Freed up for strategic work
-
-**Competing alternatives**:
-- YouTube tutorials (free but scattered)
-- Hiring a consultant (expensive, custom)
-- Doing nothing (familiar, low risk)
-
-**Refined job statement**: "Help time-starved small business owners automate their highest-volume repetitive tasks in under 2 hours, so they can reclaim 10+ hours/week without hiring or complex tech setup"
-
-**Insight**: The job isn't "learn AI"—it's "get time back fast." Make the course implementation-focused with immediate wins, not theory-heavy.