Skip to main content
ClaudeWave
Skill17k estrellas del repoactualizado 6d ago

startup-canvas

The startup-canvas skill generates a strategic framework for new products that integrates a 9-section Product Strategy Canvas with business model components covering costs and revenue streams. Use this when launching a new product or evaluating a startup concept to separate strategic decisions from financial modeling, addressing gaps that Business Model Canvas and Lean Canvas leave unresolved, such as vision, competitive defensibility, and trade-offs.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/startup-canvas && cp -r /tmp/startup-canvas/pm-product-strategy/skills/startup-canvas ~/.claude/skills/startup-canvas
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Startup Canvas

## Metadata
- **Name**: startup-canvas
- **Description**: Generate a Startup Canvas for a new product. Combines the 9-section Product Strategy Canvas with a Business Model (Cost Structure + Revenue Streams). Designed specifically for startups and new products.
- **Triggers**: startup canvas, new product canvas, startup strategy, startup business model

## Domain Context

### Startup Canvas vs Business Model Canvas vs Lean Canvas

Popular approaches like Business Model Canvas (Strategyzer) and Lean Canvas (Ash Maurya) mix strategy and business model into one artifact. The **Startup Canvas** (Paweł Huryn) separates them: 9 strategy sections from the Product Strategy Canvas + Cost Structure & Revenue Streams.

**Why not Business Model Canvas?**
- No vision — why should your team wake up every day?
- No Can't/Won't test — what stops competitors from copying you?
- No trade-offs — what you choose NOT to do creates focus
- No key metrics — how do you know the strategy is working?
- Key Partnerships and Key Resources are rarely useful for early-stage products

**Why not Lean Canvas?**
- Introduces redundancy: "Problem" overlaps with Market Segments (markets are defined by problems), "Solution" overlaps with Value Proposition (which by definition includes features)
- No vision, no trade-offs, no relative costs
- "Unfair Advantage" is too narrow — the entire strategy should be hard to copy, not just one element
- Doesn't address the holistic fit of strategic choices reinforcing each other

**When to use which:**
- **Business Model Canvas**: Established businesses, corporate strategy, investor materials
- **Lean Canvas**: Quick hypothesis testing when you just need speed
- **Startup Canvas**: New products where you need both strategic clarity AND a business model — the recommended approach

## Instructions

You are a product strategist and startup advisor designing a Startup Canvas for $ARGUMENTS.

Your task is to create a comprehensive Startup Canvas that covers both the strategic choices and the business model for a new product.

## Input Requirements
- Product or startup idea
- Target market and customer insights
- Competitive landscape
- Founder/team constraints and resources

## Startup Canvas Template

### Part 1: Product Strategy (9 Sections)

**1. Vision**
- How can we inspire people? What are we aspiring to achieve? What values do we uphold?
- Start simple. Your vision will evolve alongside the strategy.

**2. Market Segments**
- The market is defined by the problems people have (not demographics).
- Jobs to Be Done (JTBD), desired outcomes, constraints.
- What will be your first customer segment? Why this one first?

**3. Relative Costs**
- Do you optimize for low cost (like Southwest Airlines) or unique value (like Starbucks)?
- Low costs don't necessarily mean low prices.

**4. Value Proposition**
For each market segment:
- **What before**: Existing, problematic state
- **How**: Features and capabilities that change the situation
- **What after**: The benefits and outcomes
- **Alternatives**: Your unique value vs. competitors and substitutes (consider a Value Curve)

**5. Trade-offs**
- What will you NOT do? Trade-offs create focus and amplify value.
- Especially important for startups where it's tempting to chase every opportunity.

**6. Key Metrics**
- A few key metrics to measure if the product and strategy are working.
- North Star Metric and One Metric That Matters (OMTM) for this quarter.

**7. Growth**
- Product-Led Growth or Sales-Led Growth?
- Preferred channels: Social Media, SEO, Influencers, Resellers?

**8. Capabilities**
- What competencies and resources do you need to acquire?
- What do you build vs. partner for?

**9. Can't/Won't**
- What makes you think competitors can't or won't copy your strategy?
- The entire strategy should be difficult to copy — not just one element.
- Do all elements fit together and reinforce each other?

### Part 2: Business Model

**10. Cost Structure**
- Rent, hardware, licenses, technology, marketing, subscriptions, salaries.
- Which are recurring? How will they scale?

**11. Revenue Streams**
- How much money from each channel?
- Pricing approach: penetration, value-based, competitive, usage-based, SaaS?
- Is the revenue model scalable? What are the biggest uncertainties?

## Output Process
1. Define the vision and aspirational impact
2. Identify 2–3 target market segments with JTBD
3. Establish cost positioning (low cost vs premium)
4. Develop value propositions for each segment
5. List explicit trade-offs
6. Set North Star and quarterly OMTM
7. Outline growth strategy and channels
8. Document required capabilities
9. Explain defensibility (Can't/Won't test)
10. Estimate cost structure and revenue streams
11. Validate strategy coherence: do all elements reinforce each other?
12. Surface hypotheses that must be true for success
13. Suggest low-effort experiments to test key assumptions

## Notes
- The Startup Canvas separates strategy from business model — keep them distinct but connected
- Strategy should pass the Can't/Won't test: your competitors can't or won't copy the integrated set of choices
- After drafting the first version, identify and start testing hypotheses
- Mix and adapt approaches to suit your specific needs rather than following any canvas rigidly

---

### Templates

- [Startup Canvas (PPTX)](https://docs.google.com/presentation/d/1lA0SPflj5JT6jFV_jIDsqZJAYYperTFx/edit?usp=sharing&ouid=111307342557889008106&rtpof=true&sd=true)

---

### Further Reading

- [Startup Canvas: Product Strategy and a Business Model for a New Product](https://www.productcompass.pm/p/startup-canvas)
- [Product Strategy Canvas](https://www.productcompass.pm/p/product-strategy-canvas)
- [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)
- [Business Model Canvas Examples: Google Maps, Airbnb, Uber](https://www.productcompass.pm/p/business-model-canva
intended-vs-implementedSkill

The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.

shipping-artifactsSkill

The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.

ab-test-analysisSkill

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.

cohort-analysisSkill

Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.

sql-queriesSkill

Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.

brainstorm-okrsSkill

Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.

create-prdSkill

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

dummy-datasetSkill

Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.