dvy1987/agent-loom / .agents/skills/business-modeling
business-modeling
VerifiedPick the right business-model canvas (Lean Canvas, Business Model Canvas, or Value Proposition Canvas) for the stage and fill it with specifics — one segment, one primary canvas, top-3 assumptions, no fluff in the moat or channel boxes. Load when the user asks to fill a business model canvas, lean canvas, value proposition canvas, model this business, map the business model, says "fill the BMC", "make a Lean Canvas", "Value Proposition Canvas for this", "model this idea", "what's the business model", "design the business model". Sub-skill of `venture-exploration`. Hard-bans "everyone" segments, generic channels ("SEO/social/content/ads"), and "unfair advantage = AI/data/network effects" with no concrete asset. Does NOT score viability — for that use `idea-evaluation`.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.4 KB |
| references/anti-patterns.md | markdown | 3.8 KB |
| references/canvas-selector.md | markdown | 3.5 KB |
| references/canvas-templates.md | markdown | 5.2 KB |
| references/examples.md | markdown | 2.0 KB |
references/canvas-templates.md
View on GitHub# Canvas Templates
Load in `business-modeling` Step 3. Use the template matching the chosen canvas. Every box gets a specific entry OR `[HYPOTHESIS — needs validation]`.
---
## Lean Canvas Template
```markdown
# Lean Canvas: <idea>
Date: YYYY-MM-DD | Segment: <specific persona> | Stage: <pre-launch/pre-PMF>
## Problem
1. <pain #1 — most acute>
2. <pain #2>
3. <pain #3>
- Existing alternatives: <named alternatives + why each falls short>
## Customer Segments
- Primary: <specific persona in specific situation>
- Early adopters: <how they differ — usually more pain-aware, more workaround-built>
## Unique Value Proposition (UVP)
<one sentence; concrete; references the pain>
High-concept pitch: <X for Y> (only if it actually clarifies)
## Solution
1. <feature #1 — directly relieves pain #1>
2. <feature #2>
3. <feature #3>
## Channels
- Wedge channel (the one that works pre-scale): <specific>
- Later channels: <list, deprioritised>
## Revenue Streams
- Model: <subscription / transactional / usage / one-time / freemium>
- Price: $<amount> per <unit>
- Justification: <replaces $X cost / saves Y hours at $Z>
## Cost Structure
- Fixed: <hosting, salaries, tools — order of magnitude>
- Variable: <COGS per user / per transaction>
- Burn estimate: $<N>/mo at <stage>
## Key Metrics
- Acquisition: <metric, threshold>
- Activation: <metric, threshold>
- Retention: <metric, threshold>
- Revenue: <metric, threshold>
## Unfair Advantage
<concrete asset; reject "AI/network effects/team" without specifics>
- Examples that pass: proprietary dataset, exclusive partnership, founder credibility, regulatory licence, switching-cost mechanic, deep distribution access.
## Top 3 Critical Assumptions
1. **<assumption>** — Falsified if: <measurable threshold>
2. **<assumption>** — Falsified if: <measurable threshold>
3. **<assumption>** — Falsified if: <measurable threshold>
```
---
## Business Model Canvas (BMC) Template
```markdown
# BMC: <idea>
Date: YYYY-MM-DD | Segment: <specific persona> | Stage: <pre-PMF/post-PMF/pivot>
## Customer Segments
- Primary: <persona>
- Niche / multi-sided / mass / segmented: <classify>
## Value Propositions
- For <segment>: <specific value>
- Newness / performance / customisation / "getting the job done" / design / brand / price / cost reduction / risk reduction / accessibility / convenience
## Channels
- Awareness: <how segment first hears about us>
- Evaluation: <how they compare>
- Purchase: <how they buy>
- Delivery: <how they receive value>
- After-sales: <how we support>
- Wedge channel: <one specific channel>
## Customer Relationships
- Acquisition mechanic: <self-service, founder-led, dedicated CS, automated>
- Retention mechanic: <community, automation, personal assistance>
- Upsell / expansion path: <specific>
## Revenue Streams
- Stream #1: <subscription / asset sale / usage / licence / brokerage / advertising>, price <$X>, segment <Y>
- Stream #2 (if any)
## Key Resources
- Physical: <list>
- Intellectual: <data, IP, brand>
- Human: <key skills>
- Financial: <runway, credit lines>
## Key Activities
- Production: <build, ship>
- Problem-solving: <consulting, support>
- Platform / network: <maintain, moderate>
## Key Partnerships
- Strategic alliances: <named>
- Coopetition: <named>
- Buyer-supplier: <named>
- Joint ventures: <named>
## Cost Structure
- Cost-driven (lean) vs value-driven (premium): <classify>
- Fixed: <list with $>
- Variable: <list with $ per unit>
- Economies of scale / scope: <named>
## Top 3 Critical Assumptions
1. ...
2. ...
3. ...
```
---
## Value Proposition Canvas (VPC) Template
```markdown
# VPC: <idea> × <segment>
Date: YYYY-MM-DD
## Customer Profile (right side)
### Customer Jobs
- Functional: <jobs the customer is trying to get done>
- Social: <how they want to be seen>
- Emotional: <how they want to feel>
- Job context: <when, where, with whom>
### Pains
- Undesired outcomes: <costs, hassles, frustrations>
- Obstacles: <what prevents getting started, completing>
- Risks: <financial, social, technical, legal>
- Severity scale: extreme / moderate / mild — for each pain
### Gains
- Required: <what must be true for the job to be acceptable>
- Expected: <what is reasonable to expect>
- Desired: <what would be nice to have>
- Unexpected: <what would delight beyond expectations>
## Value Map (left side)
### Products & Services
- <list of what we offer>
### Pain Relievers
- For pain <X>: <how the product reduces / eliminates>
- For pain <Y>: <how the product reduces / eliminates>
### Gain Creators
- For gain <X>: <how the product produces / amplifies>
- For gain <Y>: <how the product produces / amplifies>
## Fit Assessment
- Job–Service alignment: <covered / partially covered / missed>
- Pain–Reliever alignment: <list per pain>
- Gain–Creator alignment: <list per gain>
- Unmatched pains / gains / jobs: <flagged>
- Top mismatches: <which side needs work>
## Top 3 Critical Assumptions
1. ...
2. ...
3. ...
```
---
## Quality bar (all three canvases)
- Every box has either a specific entry or `[HYPOTHESIS — needs validation]`
- Numbers are real or order-of-magnitude (call `fermi` if unknown)
- Channels box names ONE wedge
- Unfair advantage / moat is a concrete asset
- Top 3 assumptions are falsifiable with measurable thresholds
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |