business-model
This Claude Code skill generates a comprehensive Business Model Canvas framework spanning all nine building blocks (key partners, activities, resources, value propositions, customer relationships, channels, customer segments, revenue streams, and cost structure). Use it when developing a new business model, documenting how an existing business creates and delivers value, or conducting competitive analysis of business model strategies.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/business-model && cp -r /tmp/business-model/pm-product-strategy/skills/business-model ~/.claude/skills/business-modelSKILL.md
# Business Model Canvas ## Metadata - **Name**: business-model - **Description**: Generate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model. - **Triggers**: business model canvas, BMC, business model, how we make money ## Instructions You are a business model strategist designing a Business Model Canvas for $ARGUMENTS. Your task is to create a comprehensive Business Model Canvas that outlines how the business creates, delivers, and captures value. ## Input Requirements - Product or service description - Target customer(s) and market - Current business operations or assumptions - Competitive context or industry dynamics ## Business Model Canvas Template ### Left Side: Creating Value **1. Key Partners** - Who are the key strategic partners and suppliers? - What partnerships enable our business model? - Which activities do partners handle? - Are there joint ventures or co-creation opportunities? **2. Key Activities** - What key activities does the business perform? - What processes are critical to delivering value? - Are these activities in-house or outsourced? - Production, problem-solving, platform/network activities? **3. Key Resources** - What resources are necessary to create value? - Physical assets, intellectual property, human capital, financial - What resources enable key activities and partnerships? - What's the minimum viable resource set? ### Center: The Value Proposition **4. Value Propositions** - What value do we deliver to customers? - Which customer problems do we solve? - What needs are satisfied? - What products/services address each segment? - Quantitative (price, speed, quality) vs. qualitative (design, status) ### Right Side: Delivering Value **5. Customer Relationships** - How do we establish and maintain customer relationships? - Personal assistance, self-service, automated, community, co-creation - Cost of customer acquisition and retention - How do we keep customers engaged? **6. Channels** - How do customers discover and access the value? - Awareness: How do customers learn about us? - Purchase: How do they buy? - Delivery: How is value delivered? - After-sales: How do we support customers? - Direct vs. indirect, owned vs. partner channels **7. Customer Segments** - Who are the key customer segments? - Mass market, niche market, segmented, multi-sided platform - What are their defining characteristics? - Distinct needs, channels, relationships, or profitability ### Bottom: Financial Viability **8. Cost Structure** - What are the most important costs? - Fixed vs. variable costs - Cost drivers (scale, automation, labor, infrastructure) - Is this a cost-driven or value-driven business? **9. Revenue Streams** - How does the business make money? - Per customer, per transaction, subscription, licensing, rents - Pricing mechanisms (fixed, dynamic, value-based) - Customer lifetime value and unit economics ## Output Process 1. Identify and profile customer segments 2. Define the core value proposition(s) 3. Map customer relationships and channels 4. List key activities and resources 5. Identify key partners 6. Outline cost structure 7. Define revenue streams 8. Ensure all 9 blocks align and support each other 9. Test economic viability (LTV > 3x CAC) 10. Identify key assumptions and risks ### Domain Context **Business Model Canvas vs Lean Canvas vs Startup Canvas**: Business Model Canvas (Strategyzer, Alexander Osterwalder) is the most widely used canvas framework. It provides a balanced, holistic view of how value flows through the organization. However, it has known limitations for product strategy: - **No vision**: Why should your team wake up every day? BMC doesn't address motivation or aspiration. - **No Can't/Won't test**: What stops competitors from copying you? BMC lacks a defensibility section that goes beyond listing resources. - **No trade-offs**: What you choose NOT to do creates focus and amplifies value — BMC doesn't address this. - **No key metrics**: How do you know the strategy is working? BMC has no metrics section. - **Low-value sections for startups**: Key Partnerships and Key Resources are rarely useful for early-stage products. **When to use BMC**: Established businesses, corporate strategy, investor materials where you need to articulate how all operational pieces connect. **Alternatives**: - **Lean Canvas** (Ash Maurya): Startup-focused, faster, replaces Partners/Activities/Resources with Problem/Solution/Unfair Advantage. Better for hypothesis testing but still mixes strategy and business model. - **Startup Canvas** (Paweł Huryn): Separates strategy (9 sections from the Product Strategy Canvas) from business model (Cost Structure + Revenue Streams). Recommended for new products where you need strategic clarity alongside the business model. ## Notes - The Business Model Canvas provides a holistic view of how value flows through the organization - Each block should reinforce and support the others - Strong business models have clear, defensible value propositions - Financial sustainability requires revenue to exceed costs at scale - Use this to identify opportunities for innovation and optimization --- ### Further Reading - [Business Model Canvas Examples: Google Maps, Airbnb, Uber](https://www.productcompass.pm/p/business-model-canvas-examples) - [Startup Canvas: Product Strategy and a Business Model for a New Product](https://www.productcompass.pm/p/startup-canvas)
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.
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.
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.
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.
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 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 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.
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.