@rubytech/create-maxy-code 0.1.169 → 0.1.170

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

@@ -1,103 +0,0 @@
-# Pareto Analysis (80/20 Rule)
-
-## Purpose
-Identify the vital few factors that drive the majority of results, helping you focus effort where it matters most.
-
-## When to Use
-- Refining ideas to focus on highest-impact elements
-- GTM strategy (which channels, messages, or segments matter most)
-- Resource allocation decisions
-- When the idea tries to do too much
-
-## Process
-
-1. **List all factors/components**
-   - Break down your idea into discrete elements
-   - Examples: features, customer segments, marketing channels, use cases, problems solved
-
-2. **Estimate impact for each**
-   - Define "impact" based on your goal:
-     - Revenue potential
-     - Customer value created
-     - Problem severity solved
-     - Adoption likelihood
-     - Strategic importance
-   - Assign impact score (1-10 or relative ranking)
-
-3. **Estimate effort/cost for each**
-   - Resources required (time, money, complexity)
-   - Assign effort score (1-10 or relative ranking)
-
-4. **Calculate priority score (Impact-weighted)**
-   - **Priority = (Impact × 3) + (10 − Effort)**
-   - This weights Impact 3:1 over ease of implementation
-   - Range: 0 (worst) to 40 (best)
-   - Why NOT simple ratio (Impact ÷ Effort): the ratio penalises high-effort items equally regardless of how transformative they are. A medium-value easy task (5/1 = 5.0) outranks a high-value hard task (9/7 = 1.3). That's wrong — Impact is what moves the needle.
-
-5. **Sort and visualize**
-   - Sort items by Priority score (highest first)
-   - Identify the top items that deliver the majority of value
-   - Create 2x2 matrix: High/Low Impact x High/Low Effort
-   - Label quadrants by phase, not abstract categories:
-     - **MVP**: High impact, low effort (do first)
-     - **Phase 2**: High impact, high effort (strategic priorities)
-     - **Phase 3**: Low impact, low effort (if needed)
-     - **Cut/Defer**: Low impact, high effort (avoid)
-
-6. **Synthesis**
-   - What are your vital few (20%)?
-   - What can you eliminate or defer?
-   - Is your idea overly complex?
-   - Where should you focus first?
-
-## Example
-
-**Idea**: "All-in-one AI platform for solopreneurs"
-
-### Features List (ranked by Priority)
-
-| Rank | Feature | Impact | Effort | Priority |
-|------|---------|--------|--------|----------|
-| 1 | AI content generation | 9 | 7 | **30** |
-| 2 | Email marketing automation | 9 | 8 | **29** |
-| 3 | Social media scheduling | 8 | 6 | **28** |
-| 4 | Landing page builder | 8 | 9 | **25** |
-| 5 | CRM + pipeline | 7 | 9 | **22** |
-| 6 | Payment processing | 5 | 5 | **20** |
-| 7 | Analytics dashboard | 6 | 8 | **20** |
-
-Priority = (Impact × 3) + (10 − Effort)
-
-### 2x2 Matrix
-
-**MVP** (High Impact, Low Effort):
-- Social media scheduling (Impact 8, Effort 6, Priority 28)
-
-**Phase 2** (High Impact, High Effort):
-- AI content generation (Impact 9, Effort 7, Priority 30)
-- Email automation (Impact 9, Effort 8, Priority 29)
-- Landing page builder (Impact 8, Effort 9, Priority 25)
-
-**Phase 3** (Lower Impact):
-- Payment processing (Impact 5, Effort 5, Priority 20)
-
-**Cut/Defer** (Lower Impact, High Effort):
-- CRM + pipeline (Impact 7, Effort 9, Priority 22)
-- Analytics dashboard (Impact 6, Effort 8, Priority 20)
-
-### Analysis
-
-**Key change with Priority scoring:** AI content generation (Priority 30) and Email automation (Priority 29) now correctly rank above Social media scheduling (Priority 28), despite scheduling having a better ratio (1.33 vs 1.29). Impact is what moves the needle — the high-impact hard items rise to the top where they belong.
-
-### Synthesis
-
-**Insight**: Trying to build "all-in-one" dilutes focus. The vital few are content creation + distribution (AI writing, social scheduling, email). These three features solve 80% of the solopreneur's problem.
-
-**Refined idea**: "AI content creation + automated distribution platform"
-- Phase 1 MVP: AI writing + social scheduling only (quick win)
-- Phase 2: Add email automation (major project)
-- Phase 3+: Consider CRM/analytics based on user feedback
-
-**What to eliminate**: Landing page builder, CRM, analytics, payments (integrate with existing tools via API instead)
-
-**Result**: Simpler product, faster to market, clearer positioning, better focus.

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

@@ -1,291 +0,0 @@
-# Persona Development
-
-## Purpose
-Build detailed, evidence-based profiles of your ideal customers to guide product development, marketing messaging, and sales strategy.
-
-## When to Use
-- Defining target customer after initial discovery
-- Aligning team on who you're building for
-- Creating marketing and sales materials
-- Prioritizing features and roadmap
-- Training new team members on customer
-
-## Process
-
-### 1. Gather Evidence First
-
-**Personas without evidence are fiction.** Before building personas:
-
-- Conduct 15-20+ customer discovery conversations
-- Analyze existing customer data (if available)
-- Review support tickets and feedback
-- Study competitor customers
-- Observe actual user behavior
-
-### 2. Identify Persona Dimensions
-
-Build each persona across three layers:
-
-**Layer 1: Demographics (Who they are)**
-- Job title / role
-- Company size and type
-- Industry / vertical
-- Seniority level
-- Reporting structure
-- Team size (if manages others)
-- Geographic location
-
-**Layer 2: Psychographics (How they think)**
-- Goals and aspirations
-- Frustrations and fears
-- How they define success
-- What they value
-- Risk tolerance
-- Decision-making style
-- Career motivations
-
-**Layer 3: Behaviors (What they do)**
-- Where they get information
-- What communities they belong to
-- What tools they currently use
-- How they evaluate vendors
-- Who influences their decisions
-- How they spend their day
-- What triggers buying
-
-### 3. Use the Persona Template
-
-**Name and Photo:**
-Give them a memorable name and a representative photo.
-
-**Quote:**
-A one-line statement that captures their worldview.
-"I don't have time for tools that don't work immediately."
-
-**Demographics:**
-- Title: VP of Marketing
-- Company: B2B SaaS, 50-200 employees
-- Industry: Technology
-- Experience: 8-15 years
-- Location: Major metro area
-
-**Goals:**
-1. Primary goal (what they're ultimately trying to achieve)
-2. Secondary goals (supporting objectives)
-3. How they measure success
-
-**Frustrations:**
-1. Primary pain point (biggest problem)
-2. Secondary pains (related issues)
-3. What they've tried that didn't work
-
-**Psychographics:**
-- Values: [What matters to them]
-- Fears: [What keeps them up at night]
-- Motivations: [What drives them]
-- Decision style: [How they make choices]
-
-**Behaviors:**
-- Information sources: [Where they learn]
-- Communities: [Where they gather]
-- Tools: [What they currently use]
-- Buying process: [How they purchase]
-
-**Objections:**
-1. Common objection #1 and how to address
-2. Common objection #2 and how to address
-3. Deal-breakers (what would disqualify you)
-
-### 4. Validate with Real Data
-
-For each persona attribute, note the evidence:
-
-| Attribute | Claim | Evidence |
-|-----------|-------|----------|
-| Budget authority | Controls $50K+ | 12/15 interviews |
-| Pain intensity | "Critical problem" | 8/15 interviews |
-| Uses Slack | Daily communication | Observed in 10/15 |
-| Reads newsletter X | Info source | Mentioned by 5/15 |
-
-**Evidence levels:**
-- **Strong:** Mentioned by 8+ customers, observed behavior
-- **Moderate:** Mentioned by 4-7 customers
-- **Weak:** Mentioned by 1-3 customers (needs validation)
-
-### 5. Prioritize Personas
-
-If you have multiple personas, rank them:
-
-| Persona | Pain Intensity | Budget | Reachability | Priority |
-|---------|----------------|--------|--------------|----------|
-| Marketing VP | High | High | Medium | 1 |
-| Sales Manager | High | Low | High | 2 |
-| CEO | Medium | High | Low | 3 |
-
-**Focus on one primary persona initially.** Trying to serve multiple personas simultaneously dilutes your value proposition.
-
-### 6. Create the Buying Committee
-
-B2B purchases rarely involve one person. Map the committee:
-
-**User Buyer:** Uses the product daily
-- What they care about: Ease of use, saves them time
-- How to win them: Demo, trial, workflow fit
-
-**Economic Buyer:** Approves the budget
-- What they care about: ROI, risk mitigation
-- How to win them: Business case, case studies
-
-**Technical Buyer:** Evaluates fit with stack
-- What they care about: Integration, security, compliance
-- How to win them: Technical docs, architecture review
-
-**Champion:** Advocates for purchase internally
-- What they care about: Making the right choice
-- How to win them: Arm them with internal selling materials
-
-### 7. Keep Personas Alive
-
-**Update regularly:**
-- After every 10 customer conversations
-- After product launches or pivots
-- When you see changes in conversion patterns
-
-**Use in decisions:**
-- "Would [Persona Name] use this feature?"
-- "Where would [Persona Name] hear about us?"
-- "What would [Persona Name] object to?"
-
-**Share broadly:**
-- Print and post in office
-- Reference in meetings
-- Include in onboarding docs
-
-### 8. Common Mistakes
-
-**Creating personas without evidence:**
-"I think our customer is..." = fiction
-
-**Too many personas too early:**
-Start with one, expand when validated
-
-**Generic personas:**
-"Marketing professional" is not specific enough
-
-**Outdated personas:**
-Never updated after initial creation
-
-**Persona worship:**
-Using personas to avoid talking to real customers
-
-### 9. Synthesis
-
-After developing your persona:
-- Does this persona match who's actually buying?
-- Can you find more of this persona easily?
-- Does your product truly solve their primary pain?
-- Does your messaging resonate with their worldview?
-- What would make this persona a perfect fit for you?
-
-## Example
-
-**Product**: AI-powered content calendar for marketing teams
-
-### Primary Persona: "Marketing Manager Maya"
-
-**Quote:**
-"I spend more time planning what to post than actually creating content."
-
-**Photo:** Professional woman, 30s, on laptop in modern office
-
-### Demographics
-
-| Attribute | Detail | Evidence |
-|-----------|--------|----------|
-| Title | Marketing Manager | 14/20 interviews |
-| Company size | 50-200 employees | 12/20 interviews |
-| Team size | 2-5 direct reports | 10/20 interviews |
-| Industry | B2B SaaS | 11/20 interviews |
-| Experience | 5-10 years in marketing | 15/20 interviews |
-| Location | US, urban | Observed |
-
-### Psychographics
-
-**Goals:**
-1. Build a consistent, high-quality content presence
-2. Generate more MQLs from content
-3. Get promoted to Director
-
-**Frustrations:**
-1. "We're always scrambling to figure out what to post next"
-2. "My team spends hours on planning meetings"
-3. "I can't prove content ROI to leadership"
-
-**Values:**
-- Efficiency over perfection
-- Data-driven decisions
-- Team collaboration
-
-**Fears:**
-- Looking disorganized to leadership
-- Falling behind competitors
-- Missing opportunities due to poor planning
-
-**Decision style:**
-- Researches thoroughly before deciding
-- Gets input from team
-- Needs to justify spend to VP
-
-### Behaviors
-
-**Information sources:**
-- Marketing newsletters (Morning Brew, theSkimm)
-- LinkedIn content creators
-- Podcasts during commute
-- Slack communities (Demand Gen group)
-
-**Current tools:**
-- Spreadsheets for content calendar (83%)
-- Trello/Asana for task management (65%)
-- Hootsuite/Buffer for scheduling (70%)
-- Google Analytics for measurement
-
-**Buying process:**
-1. Identifies problem through frustration
-2. Googles solutions
-3. Signs up for free trials
-4. Gets team feedback
-5. Builds business case for VP
-
-### Objections and Responses
-
-| Objection | Response |
-|-----------|----------|
-| "We already use spreadsheets" | "Most teams we work with used spreadsheets. They save 5+ hours/week after switching." |
-| "I need buy-in from my VP" | "Here's an ROI calculator and case study from similar companies." |
-| "What if AI suggestions are off-brand?" | "You train the AI on your brand voice. It learns your style." |
-
-### The Buying Committee
-
-| Role | Person | Care About | Win Them |
-|------|--------|------------|----------|
-| User Buyer | Maya | Ease of use | Free trial |
-| Economic Buyer | VP Marketing | ROI, efficiency | Business case |
-| Technical Buyer | Marketing Ops | Integration | Zapier, API docs |
-| Champion | Maya | Looking good | Success metrics |
-
-### Using Maya in Decisions
-
-**Product:** "Would Maya understand this feature in 10 seconds?"
-
-**Marketing:** "Where would Maya discover us?"
-→ LinkedIn ads to Marketing Manager titles
-→ Sponsor marketing podcasts
-→ Content in Demand Gen Slack
-
-**Sales:** "What would Maya object to?"
-→ Prepare ROI calculator
-→ Have case study from similar company ready
-→ Offer team trial, not individual
-
-**Insight:** Maya helped the team stop debating features in abstract and start asking "Does Maya need this?" When they added an AI feature, they tested it against Maya's mental model—would she trust AI suggestions? This led to a "human review" workflow that increased adoption.

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

@@ -1,225 +0,0 @@
-# Pivot Types
-
-## Purpose
-Understand the different ways a startup can change direction while preserving validated learning, making pivots strategic rather than random.
-
-## When to Use
-- Validation experiments are failing despite tuning efforts
-- Product-market fit remains elusive
-- Need to decide between persevering and changing direction
-- Want to explore alternative paths for a struggling idea
-- Current strategy isn't working but underlying opportunity exists
-
-## Process
-
-### 1. Recognize When to Pivot
-
-**Signs a pivot may be needed:**
-- Metrics have plateaued despite multiple improvement attempts
-- Customer feedback reveals you're solving the wrong problem
-- Growth is powered only by unsustainable tactics
-- Unit economics don't work (CAC > LTV)
-- Team has lost conviction in current direction
-- Competitors are winning despite your efforts
-
-**Signs to persevere instead:**
-- Metrics show consistent improvement
-- Customer feedback is increasingly positive
-- Clear hypotheses about what will improve results
-- Product changes drive measurable improvements
-- Team believes in the direction
-
-### 2. The Ten Pivot Types
-
-**1. Zoom-in Pivot**
-A single feature becomes the entire product.
-- **When:** One feature gets all the engagement; the rest is ignored
-- **Example:** Flickr pivoted from a game (where photo sharing was one feature) to photo sharing platform
-- **Signal:** Usage concentrated in one area; customers asking for more of that specific feature
-
-**2. Zoom-out Pivot**
-The entire product becomes a single feature of a larger product.
-- **When:** Current product is too narrow to sustain a business
-- **Example:** Adding marketplace features around a single-purpose tool
-- **Signal:** Customers saying "I wish it also did X, Y, Z"
-
-**3. Customer Segment Pivot**
-Same product solves a real problem for a different customer.
-- **When:** Product works but for different people than expected
-- **Example:** Selling collaboration software to hospitals instead of offices
-- **Signal:** Unexpected customer segments showing strong adoption; target segment not buying
-
-**4. Customer Need Pivot**
-Serving the same customers but solving a different problem.
-- **When:** You understand the customer but not their most important problem
-- **Example:** Realizing customers want scheduling help, not calendar features
-- **Signal:** During conversations, customers keep bringing up different pain points
-
-**5. Platform Pivot**
-Changing from application to platform (or vice versa).
-- **When:** Single application can't capture full value; or platform is too complex to start
-- **Example:** Starting as a service, becoming a platform (AWS from Amazon's retail)
-- **Signal:** Customers wanting to customize/extend; or struggling to get platform adoption
-
-**6. Business Architecture Pivot**
-Switching between high margin/low volume and low margin/high volume.
-- **When:** Original model doesn't match market reality
-- **Example:** Moving from enterprise sales ($100K deals) to self-serve SaaS ($100/month)
-- **Signal:** Sales cycle too long; or self-serve users wanting more support
-
-**7. Value Capture Pivot**
-Changing how you monetize (business model change).
-- **When:** Current pricing model doesn't align with value delivered
-- **Example:** Moving from subscription to usage-based pricing
-- **Signal:** Customers churning because they don't use enough; or heavy users feeling constrained
-
-**8. Engine of Growth Pivot**
-Changing how you acquire and retain customers.
-- **When:** Current growth engine isn't working
-- **Example:** Moving from viral growth to paid acquisition
-- **Signal:** Viral coefficient below 1; or paid acquisition ROI positive
-
-**9. Channel Pivot**
-Changing how you reach customers.
-- **When:** Current channel doesn't work for your customers
-- **Example:** Moving from direct sales to partner distribution
-- **Signal:** CAC too high through current channel; or customers expecting different buying experience
-
-**10. Technology Pivot**
-Achieving the same solution through different technology.
-- **When:** New technology enables better delivery of same value
-- **Example:** Rebuilding desktop software as cloud application
-- **Signal:** Technology limitations blocking growth; or new tech creating opportunities
-
-### 3. Choosing the Right Pivot
-
-**Ask these diagnostic questions:**
-
-**Do customers want what we're building?**
-- No → Customer Need Pivot or Customer Segment Pivot
-- Yes → Look at other issues
-
-**Are we reaching the right customers?**
-- No → Customer Segment Pivot or Channel Pivot
-- Yes → Look at other issues
-
-**Can we make money from this?**
-- No → Value Capture Pivot or Business Architecture Pivot
-- Yes → Look at other issues
-
-**Can we grow this?**
-- No → Engine of Growth Pivot or Channel Pivot
-- Yes → Keep iterating
-
-**Is our product scope right?**
-- Too narrow → Zoom-out Pivot or Platform Pivot
-- Too broad → Zoom-in Pivot
-
-### 4. Executing the Pivot
-
-**Before pivoting:**
-1. Document what you've learned (preserve the learning)
-2. Clarify what's changing and what's staying the same
-3. Set new hypotheses to test
-4. Get team alignment on the new direction
-
-**During the pivot:**
-1. Treat it as a new series of Build-Measure-Learn loops
-2. Don't throw away everything—keep what's working
-3. Move quickly—a pivot isn't a break, it's a change of direction
-4. Re-validate core assumptions for the new direction
-
-**After pivoting:**
-1. Establish new baseline metrics
-2. Set new success criteria
-3. Communicate the change to stakeholders
-4. Don't look back—commit to learning about the new direction
-
-### 5. Common Mistakes
-
-**Pivoting too early:** Not giving the current strategy enough time/iterations
-
-**Pivoting too late:** Persevering despite clear evidence of failure
-
-**Pseudo-pivot:** Changing randomly without clear hypothesis
-
-**Forgetting the learning:** Throwing away insights from the previous direction
-
-**Pivoting without team alignment:** Creates confusion and reduces commitment
-
-### 6. Synthesis
-
-When considering a pivot:
-- What have we learned that's valuable regardless of direction?
-- Which pivot type best preserves our learning?
-- What's the hypothesis we're testing with the new direction?
-- What would success look like in 90 days?
-- What would make us pivot again (failure criteria)?
-
-## Example
-
-**Original Idea**: "B2B SaaS for enterprise meeting scheduling"
-
-### The Journey
-
-**Initial metrics (3 months in):**
-- Target customers: Enterprise (1000+ employees)
-- Sales cycle: 6+ months
-- Pipeline: 3 deals, none closed
-- Burn rate: $150K/month
-- Runway: 8 months
-
-### Pivot Analysis
-
-**The symptoms:**
-- Enterprise sales cycles too long for our runway
-- Procurement process killing deals
-- Product works but customers can't buy fast enough
-- Individual employees love it; IT/purchasing blocks it
-
-**Pivot options considered:**
-
-1. **Business Architecture Pivot:** Enterprise → SMB
-   - Shorter sales cycles
-   - Self-serve possible
-   - Lower contract values
-
-2. **Channel Pivot:** Direct sales → Bottoms-up adoption
-   - Let individuals use for free
-   - Convert to team plans
-   - Enterprise follows
-
-3. **Customer Segment Pivot:** Enterprise → Startups/SMB
-   - Faster decisions
-   - Lower complexity
-   - Growth potential if we scale with them
-
-### Decision: Combination Pivot
-
-**Business Architecture + Customer Segment:**
-- Target: SMB companies (50-500 employees)
-- Model: Self-serve SaaS ($29-99/user/month)
-- Growth: Bottoms-up (free trial → team → company)
-
-**What we preserved:**
-- Core product (works well)
-- Enterprise learnings (useful for future expansion)
-- One enterprise pilot customer (case study)
-
-**New hypotheses:**
-- SMB decision-makers can buy in <30 days
-- Self-serve onboarding will work
-- Pricing at $49/user/month achieves positive unit economics
-
-### Post-Pivot Metrics (3 months later)
-
-- Target customers: SMB (50-500 employees)
-- Sales cycle: <30 days (✓)
-- Paying customers: 23 companies
-- MRR: $18K
-- CAC: $450
-- LTV (projected): $2,700
-
-**Insight:** The pivot preserved the core product value while changing the business architecture and customer segment. The technology and team capabilities were assets; the original go-to-market strategy was the liability.
-
-**Next decision point:** If MRR reaches $50K in 6 months, expand team. If not, consider Engine of Growth pivot (current: paid acquisition → test: viral/referral).