business-model-canvas▌
scientiacapital/skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
<quick_start>
- ›Generate a canvas:
<quick_start> Generate a canvas:
/business-model canvas for [company/idea]
Claude will analyze all 9 blocks:
- Customer Segments (who are we serving?)
- Value Propositions (what value do we deliver?)
- Channels (how do we reach customers?)
- Customer Relationships (how do we engage?)
- Revenue Streams (how do we make money?)
- Key Resources (what do we need?)
- Key Activities (what must we do?)
- Key Partnerships (who helps us?)
- Cost Structure (what does it cost?) </quick_start>
<the_9_blocks>
1. Customer Segments
Question: For whom are we creating value? Who are our most important customers?
Types:
| Type | Description | Example |
|---|---|---|
| Mass Market | No distinction between segments | Consumer electronics |
| Niche Market | Specific, specialized segment | Luxury goods |
| Segmented | Slightly different needs | Bank retail vs private |
| Diversified | Unrelated segments | Amazon (retail + AWS) |
| Multi-sided | Interdependent segments | Credit cards (merchants + cardholders) |
2. Value Propositions
Question: What value do we deliver? Which problems do we solve?
Value Types:
- Newness - New needs customers didn't know they had
- Performance - Improving product/service performance
- Customization - Tailoring to specific needs
- Getting the Job Done - Simply helping get things done
- Design - Superior design and aesthetics
- Brand/Status - Value from using a specific brand
- Price - Offering similar value at lower price
- Cost Reduction - Helping customers reduce costs
- Risk Reduction - Reducing risks customers incur
- Accessibility - Making products available to new segments
- Convenience/Usability - Making things easier to use
3. Channels
Question: How do we reach our customers? Which channels work best?
Channel Phases:
- Awareness - How do we raise awareness?
- Evaluation - How do we help customers evaluate?
- Purchase - How do we allow customers to purchase?
- Delivery - How do we deliver value?
- After-sales - How do we provide post-purchase support?
Channel Types:
| Type | Owned | Partner |
|---|---|---|
| Direct | Sales force, web sales, own stores | - |
| Indirect | - | Partner stores, wholesalers |
4. Customer Relationships
Question: What type of relationship does each segment expect?
Relationship Types:
- Personal Assistance - Human interaction during/after sale
- Dedicated Personal Assistance - Dedicated representative
- Self-Service - No direct relationship, all resources provided
- Automated Services - Mix of self-service + automation
- Communities - User communities for knowledge exchange
- Co-creation - Customer involvement in value creation
5. Revenue Streams
Question: For what value are customers willing to pay? How do they pay?
Revenue Types:
| Type | Description | Pricing |
|---|---|---|
| Asset Sale | Selling ownership rights | Fixed/Dynamic |
| Usage Fee | Pay per use of service | Per unit |
| Subscription | Recurring access fee | Monthly/Annual |
| Lending/Leasing | Temporary right to use | Per period |
| Licensing | Intellectual property rights | Per license |
| Brokerage Fees | Intermediation fee | % of transaction |
| Advertising | Fees for advertising | CPM/CPC/CPA |
Pricing Mechanisms:
- Fixed: List price, feature-dependent, segment-dependent, volume-dependent
- Dynamic: Negotiation, yield management, real-time market, auctions
6. Key Resources
Question: What key resources does our value proposition require?
Resource Categories:
| Category | Examples |
|---|---|
| Physical | Facilities, equipment, vehicles, inventory, materials |
| Intellectual | Brands, patents, copyrights, proprietary knowledge, databases |
| Human | Creative talent, expertise, experience, skills |
| Financial | Cash, credit lines, stock options, guarantees |
7. Key Activities
Question: What key activities does our value proposition require?
Activity Categories:
- Production - Designing, making, delivering products (manufacturing)
- Problem Solving - Finding solutions to individual problems (consulting)
- Platform/Network - Platform development, service provisioning, promotion (tech)
8. Key Partnerships
Question: Who are our key partners and suppliers?
Partnership Types:
| Type | Purpose | Example |
|---|---|---|
| Strategic Alliance | Non-competitors | Airlines + Hotels |
| Coopetition | Competitors partnering | Samsung + Apple (components) |
| Joint Venture | New business development | Sony Ericsson |
| Buyer-Supplier | Assured supplies | Car manufacturers + suppliers |
Partnership Motivations:
- Optimization and economies of scale
- Reduction of risk and uncertainty
- Acquisition of resources and activities
9. Cost Structure
Question: What are the most important costs in our business model?
Cost Focus:
| Approach | Description | Example |
|---|---|---|
| Cost-Driven | Minimize costs wherever possible | Budget airlines, Walmart |
| Value-Driven | Focus on value creation | Luxury hotels, premium brands |
Cost Characteristics:
- Fixed Costs - Same regardless of volume (salaries, rent)
- Variable Costs - Vary with production volume (materials)
- Economies of Scale - Lower cost per unit with volume
- Economies of Scope - Lower cost with broader operations
</the_9_blocks>
<canvas_generation_algorithm>
Canvas Generation Process
Step 1: Identify Customer Segments
For each potential segment:
- Define demographics/firmographics
- Assess market size
- Evaluate accessibility
- Score attractiveness (1-10)
Prioritize: Focus on top 2-3 segments
Step 2: Define Value Propositions
For each priority segment:
- List jobs-to-be-done
- Identify pains to relieve
- Identify gains to create
- Match to value types above
Map: segment → value proposition(s)
Step 3: Design Channels
For each channel phase:
- Awareness: [channels]
- Evaluation: [channels]
- Purchase: [channels]
- Delivery: [channels]
- After-sales: [channels]
Optimize: Cost vs reach vs customer preference
Step 4: Define Customer Relationships
For each segment:
- Determine relationship type
- Consider acquisition cost
- Plan retention strategy
- Define upsell path
Step 5: Establish Revenue Streams
For each value proposition:
- Select revenue type
- Choose pricing mechanism
- Estimate willingness to pay
- Project revenue potential
Step 6: Identify Key Resources
For value propositions + channels + relationships:
- List required physical resources
- List required intellectual resources
- List required human resources
- List required financial resources
Step 7: Define Key Activities
For each key resource:
- Define activities to acquire
- Define activities to maintain
- Define activities to leverage
Categorize: Production / Problem Solving / Platform
Step 8: Establish Key Partnerships
For each activity not core to business:
- Evaluate build vs buy vs partner
- Identify potential partners
- Define partnership type
- Establish terms
Step 9: Calculate Cost Structure
Sum all costs:
- Fixed costs (resources, overhead)
- Variable costs (per unit)
- Partnership costs
Determine: Cost-driven or Value-driven approach
</canvas_generation_algorithm>
<output_format>
Business Model Canvas Output
Visual Canvas Layout
┌─────────────────┬─────────────────┬─────────────────┬─────────────────┬─────────────────┐
│ Key Partners │ Key Activities │ Value │ Customer │ Customer │
│ │ │ Propositions │ Relationships │ Segments │
│ • Partner 1 │ • Activity 1 │ │ │ │
│ • Partner 2 │ • Activity 2 │ • Value 1 │ • Type 1 │ • Segment 1 │
│ ├─────────────────┤ • Value 2 │ • Type 2 │ • Segment 2 │
│ │ Key Resources │ │ │ │
│ │ │ ├─────────────────┤ │
│ │ • Resource 1 │ │ Channels │ │
│ │ • Resource 2 │ │ │ │
│ │ │ │ • Channel 1 │ │
│ │ │ │ • Channel 2 │ │
├─────────────────┴─────────────────┴─────────────────┴─────────────────┴─────────────────┤
│ Cost Structure │ Revenue Streams │
│ │ │
│ Fixed: $X │ • Stream 1: $Y │
│ Variable: $X per unit │ • Stream 2: $Z │
└───────────────────────────────────┴─────────────────────────────────────────────────────┘
Table Format
| Block | Content |
|---|---|
| Customer Segments | [List segments] |
| Value Propositions | [List propositions] |
| Channels | [List channels by phase] |
| Customer Relationships | [List relationship types] |
| Revenue Streams | [List streams with pricing] |
| Key Resources | [List by category] |
| Key Activities | [List activities] |
| Key Partnerships | [List partners and purpose] |
| Cost Structure | [List costs, approach] |
</output_format>
<validation_questions>
Canvas Validation Checklist
Customer Segments
- Are segments clearly defined and distinct?
- Is market size quantified?
- Are they profitable to serve?
Value Propositions
- Does it solve a real problem or satisfy a need?
- Is it differentiated from competitors?
- Is value clearly articulated?
Channels
- Are channels cost-efficient?
- Do they reach target segments effectively?
- Are they integrated across phases?
Customer Relationships
- Do relationships match segment expectations?
- Are acquisition costs sustainable?
- Is there a retention strategy?
Revenue Streams
- Are customers willing to pay?
- Is pricing competitive yet profitable?
- Are revenue streams diversified?
Key Resources
- Are all critical resources identified?
- Are intellectual assets protected?
- Is human capital sustainable?
Key Activities
- Are activities aligned with value proposition?
- Are processes documented and scalable?
- Is quality maintained?
Key Partnerships
- Are partnerships strategically valuable?
- Are dependencies manageable?
- Are terms favorable?
Cost Structure
- Are all costs accounted for?
- Is the model profitable at scale?
- Are there cost optimization opportunities?
</validation_questions>
<canvas_metrics>
Canvas Health Metrics
Viability Score (0-100)
Customer fit: (segment_clarity + value_alignment) / 2 × 20
Channel efficiency: (reach + cost_efficiency) / 2 × 15
Relationship depth: (retention + satisfaction) / 2 × 15
Revenue potential: (streams_diversity + pricing_power) / 2 × 20
Cost efficiency: (margin + scalability) / 2 × 15
Resource strength: (capabilities + sustainability) / 2 × 15
──────────────────────────────────────────────────────────────
Total: Sum of above (max 100)
Key Ratios
| Ratio | Formula | Healthy Range |
|---|---|---|
| CAC | Total acquisition cost / New customers | Industry-dependent |
| LTV:CAC | Lifetime value / Acquisition cost | > 3:1 |
| Gross Margin | (Revenue - COGS) / Revenue | > 50% for SaaS |
| Burn Rate | Monthly cash outflow | < 1/12 of runway |
</canvas_metrics>
<example_session>
Example: AI-Powered CRM Startup
User: Create a business model canvas for an AI-powered CRM for small businesses
Customer Segments
- Primary: Small businesses (10-50 employees) in service industries
- Secondary: Solopreneurs and freelancers
- Characteristics: Tech-savvy, growth-oriented, limited IT resources
Value Propositions
- AI automates data entry from emails/calls (saves 5+ hours/week)
- Predictive lead scoring (increases close rate 20%)
- Natural language queries ("Show my hottest leads in Texas")
- Affordable pricing (1/3 of enterprise CRM cost)
Channels
- Awareness: Content marketing, SEO, partner referrals
- Evaluation: Free trial, demo videos, ROI calculator
- Purchase: Self-service online checkout
- Delivery: Cloud SaaS, browser + mobile apps
- After-sales: In-app chat, knowledge base, email support
Customer Relationships
- Self-service: Most interactions automated
- Automated: AI-powered onboarding, tips, alerts
- Community: User forum, template sharing
- Personal: High-touch for annual plans (10+ seats)
Revenue Streams
- Subscription: $29/user/month (monthly) or $19/user/month (annual)
- Premium Features: AI analytics add-on +$10/user/month
- Integration Marketplace: 20% rev share on partner integrations
Key Resources
- Proprietary AI/ML models (NLP, prediction)
- Cloud infrastructure (AWS/GCP)
- Engineering team (10 FTEs)
- Customer success team (3 FTEs)
Key Activities
- AI model training and improvement
- Platform development and maintenance
- Customer acquisition and onboarding
- Integration partnerships
Key Partnerships
- Cloud providers (AWS, GCP) - infrastructure
- Communication platforms (Twilio, email APIs) - integrations
- Accounting software (QuickBooks, Xero) - data sync
- Referral partners (consultants, VARs) - distribution
Cost Structure
- Fixed: Salaries ($800K/yr), office ($50K/yr), tools ($30K/yr)
- Variable: Cloud costs ($2/user/month), support ($1/user/month)
- Approach: Value-driven (premium AI features justify pricing)
Canvas Score: 78/100
- Customer fit: 18/20 (strong segment-value match)
- Channel efficiency: 12/15 (need more paid acquisition)
- Relationship depth: 11/15 (automation good, retention TBD)
- Revenue potential: 16/20 (pricing competitive, upsell path clear)
- Cost efficiency: 12/15 (good unit economics)
- Resource strength: 9/15 (AI talent competitive market)
</example_session>
<success_criteria> Canvas is successful when:
- All 9 building blocks are populated with specific, actionable content
- Customer segments are clearly defined with quantified market size
- Value propositions address real problems with clear differentiation
- Revenue streams match customer willingness to pay
- Cost struct
How to use business-model-canvas on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add business-model-canvas
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches business-model-canvas from GitHub repository scientiacapital/skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate business-model-canvas. Access the skill through slash commands (e.g., /business-model-canvas) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★59 reviews- ★★★★★Kwame Brown· Dec 24, 2024
We added business-model-canvas from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Aanya Verma· Dec 20, 2024
I recommend business-model-canvas for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Soo Bansal· Dec 8, 2024
Keeps context tight: business-model-canvas is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Dev Malhotra· Dec 4, 2024
Useful defaults in business-model-canvas — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Soo Srinivasan· Nov 27, 2024
Registry listing for business-model-canvas matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Arya Dixit· Nov 19, 2024
Useful defaults in business-model-canvas — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kwame Jackson· Nov 15, 2024
Solid pick for teams standardizing on skills: business-model-canvas is focused, and the summary matches what you get after install.
- ★★★★★Soo Rao· Oct 18, 2024
business-model-canvas reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★William Bansal· Oct 10, 2024
I recommend business-model-canvas for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ama Patel· Oct 6, 2024
business-model-canvas has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 59