borghei/Claude-Skills / project-management/strategy-frameworks/business-model-canvas
business-model-canvas
VerifiedBuilds and audits a nine-block Business Model Canvas, tracing each segment through value, channel and revenue and naming the riskiest assumptions. Use when designing, refreshing or stress-testing a business model.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.5 KB |
| assets/canvas_template.md | markdown | 3.6 KB |
| assets/sample_canvas.json | config | 2.7 KB |
| assets/sample_canvas_flawed.json | config | 409 B |
| references/canvas-framework.md | markdown | 9.3 KB |
| references/examples-anti-patterns.md | markdown | 6.3 KB |
| scripts/canvas_validator.py | script | 15.6 KB |
references/canvas-framework.md
View on GitHub# Business Model Canvas — Framework Reference
The 9 blocks, in working depth.
## 1. Customer Segments
The groups of people or organizations the company aims to serve.
### Segment archetypes
- **Mass market** — large undifferentiated group (consumer electronics)
- **Niche market** — specific specialized segment (B2B vertical SaaS)
- **Segmented** — distinct segments with slightly different needs (retail banks)
- **Diversified** — unrelated segments (Amazon Retail + AWS)
- **Multi-sided platform** — interdependent segments (Visa: cardholders + merchants)
### Sharp segment statements
- "Mid-market SaaS companies (200-2000 employees) buying their first compliance tool"
- "Vegan home cooks in urban North America, age 25-45, with kitchen confidence"
Not: "businesses that want to be more efficient" — too generic.
### Common errors
- One segment that's really 4 segments (different needs / pricing / channels)
- Segments where you can't articulate the difference in value prop
- Segments you can't reach via your channels
## 2. Value Propositions
The bundle of products/services that creates value for a specific segment.
### Value types
- **Newness** — meets a previously unaddressed need
- **Performance** — better than existing alternatives
- **Customization** — tailored to specific needs
- **Getting the job done** — helps perform a specific job (JTBD framing)
- **Design** — superior aesthetics or experience
- **Brand/status** — value from using the brand itself
- **Price** — lower cost for same value
- **Cost reduction** — reduces customer's costs
- **Risk reduction** — reduces customer's risk
- **Accessibility** — makes available what was inaccessible
- **Convenience / usability** — easier to use
### Sharp VP statements
- "Removes 80% of GDPR DSAR fulfillment time for European tech companies"
- "Lets non-technical operators run k8s workloads without learning k8s"
### Common errors
- VP that lists features instead of value delivered
- One VP across all segments (each segment needs its own)
- VP not aligned with customer's actual JTBD
## 3. Channels
How the value prop is delivered to customer segments.
### Channel phases
1. **Awareness** — how customers learn we exist
2. **Evaluation** — how they evaluate our offer
3. **Purchase** — how they buy
4. **Delivery** — how value reaches them
5. **After-sales** — how we support post-purchase
### Channel types
- Own + direct (sales force, web direct)
- Own + indirect (own retail, white label)
- Partner direct (partner sales)
- Partner indirect (wholesale, partner retail)
### Common errors
- Listing the channel without specifying which phase
- Pretending one channel does all phases when it can't
- Not matching channel economics to segment (enterprise direct sales for $50/mo product)
## 4. Customer Relationships
The type of relationship established with each segment.
### Relationship types
- **Personal assistance** — human interaction (sales / CS)
- **Dedicated personal assistance** — named account manager
- **Self-service** — customer helps themselves
- **Automated services** — recognized + tailored automation
- **Communities** — user-to-user (peer support)
- **Co-creation** — customers participate in value creation
### Per-segment design
Different segments need different relationships. Enterprise = personal assistance.
SMB / PLG = self-service + community. Same product, different models.
### Common errors
- "Excellent customer service" for everyone (impossible economics for self-serve)
- Self-service-only for enterprise (loses deals)
- No community when network effects could compound
## 5. Revenue Streams
The cash a company generates from each segment (revenue - costs = earnings).
### Stream types
- **Asset sale** — selling ownership of a product
- **Usage fee** — pay per use (consumption-based)
- **Subscription fee** — pay for continuous access
- **Lending / leasing / renting** — pay for temporary access
- **Licensing** — pay to use IP
- **Brokerage fee** — pay for connecting parties
- **Advertising** — pay for placement
- **Freemium** — free tier + paid upgrades
### Pricing mechanisms
- **Fixed list price** — published, non-negotiable
- **Bargaining / negotiation** — sales-led, deal-by-deal
- **Auction** — competitive bidding
- **Market-dependent** — varies with market conditions
- **Volume-dependent** — discount on volume
- **Yield management** — varies with inventory / time
### Common errors
- Revenue stream that doesn't match how the customer wants to pay
- Mixing fixed + usage + subscription without clear tiering
- Pricing the wrong dimension (per seat when value is per transaction)
## 6. Key Resources
The assets needed to make the model work.
### Resource types
- **Physical** — facilities, equipment, inventory, distribution
- **Intellectual** — brands, knowledge, patents, copyrights, customer data
- **Human** — key team members, sales force, R&D
- **Financial** — cash, credit lines, stock option pools
### Common errors
- Listing generic resources (a SaaS company "needs computers")
- Missing the truly differentiating resources (which is your moat?)
- Confusing "would be nice" with "must have"
## 7. Key Activities
The most important things the company must do to make the model work.
### Activity categories
- **Production** — designing + making + delivering a product (manufacturers)
- **Problem solving** — finding solutions to individual customer problems (consultancies, hospitals)
- **Platform / network** — managing a multi-sided platform (eBay, Visa)
Most companies do all three to some extent; categorize by primary activity.
### Common errors
- Listing 20 activities (everything = nothing)
- Activities that don't match the value prop (R&D listed but value is service)
## 8. Key Partnerships
The network of suppliers and partners that make the model work.
### Partnership types
- **Strategic alliance** between non-competitors
- **Coopetition** — strategic partnership between competitors
- **Joint venture** — new business
- **Buyer-supplier** — reliable supply chain
### Motivations
- Optimization + economies of scale (outsource what's not differentiating)
- Reduction of risk + uncertainty
- Acquisition of particular resources / activities
### Common errors
- Partnerships listed without specifying what each party gives + gets
- Over-reliance on a single partner = strategic risk
- Partnership-heavy model without coordination overhead accounted for
## 9. Cost Structure
The major costs incurred to operate the business model.
### Cost classifications
- **Fixed costs** — same regardless of volume (salary, rent)
- **Variable costs** — scale with volume (raw materials, hosting per user)
- **Economies of scale** — cost advantages as output expands
- **Economies of scope** — cost advantages from larger scope (shared marketing)
### Business model orientation
- **Cost-driven** — minimize costs (low-cost airlines)
- **Value-driven** — focus on value creation (luxury hotels)
### Common errors
- Costs that don't sum to the implied revenue model
- Forgetting customer acquisition cost
- Forgetting infrastructure scaling cost
- Forgetting human capital cost (the biggest line item in most modern companies)
## 10. Patterns — common business model archetypes
### Subscription SaaS
- Segments: defined verticals + sizes
- VP: ongoing access to capability + improvements
- Channels: web + sales-assisted
- Relationship: self-service + CS
- Revenue: recurring subscription (per-seat / per-tier / hybrid)
- Resources: product + brand + customer base
- Activities: R&D + sales + support
- Partnerships: technology integrations
- Costs: people-heavy (engineering, sales, CS)
### Multi-sided platform
- Segments: 2+ interdependent
- VP: matching / discovery / coordination across sides
- Channels: web + ecosystem
- Relationship: self-service for both sides + curation
- Revenue: transaction fee, listing fee, advertising
- Resources: platform + network + brand
- Activities: platform development + matching + trust + safety
- Partnerships: payment, identity, distribution
- Costs: platform engineering + sales to both sides + trust ops
### Marketplace
- Segments: supply + demand
- VP: discovery + trust + transaction efficiency
- Channels: web (web-first); mobile
- Relationship: self-service + curation
- Revenue: transaction fee, premium listings
- Resources: marketplace + brand + ratings/reviews
- Activities: matching + trust + safety + dispute resolution
- Partnerships: payment, logistics, identity
- Costs: tech + marketing + trust ops + chargebacks
### Open-source + services
- Segments: developer + enterprise
- VP: free core + paid expertise + enterprise features
- Channels: GitHub + sales-led for enterprise
- Relationship: community-led for free; assisted for paid
- Revenue: enterprise subscription + services + support
- Resources: codebase + community + brand
- Activities: core dev + community + sales
- Partnerships: integrations + cloud marketplaces
- Costs: engineering + community + sales
## 11. Reading the canvas
A coherent canvas:
- Each Segment has a clear Value Prop
- Each Value Prop reaches its Segment via Channels
- Each Segment has a Relationship pattern matching channel + value
- Revenue Streams flow from each Segment
- Costs map to Resources + Activities + Partnerships
- The math works: revenue per segment > cost per segment, eventually
An incoherent canvas has gaps in the chain. Walk each segment end-to-end.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |