borghei/Claude-Skills / project-management/strategy-frameworks/lean-canvas
lean-canvas
VerifiedSketches a one-page startup model as testable hypotheses: problem, early adopters, value proposition, unfair advantage, riskiest assumptions. Use at the idea, pre-product-market-fit or pivot stage, or for a fast model.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.8 KB |
| assets/lean_canvas_template.md | markdown | 2.3 KB |
| assets/sample_lean_canvas.json | config | 3.0 KB |
| assets/sample_lean_canvas_flawed.json | config | 638 B |
| references/lean-canvas-framework.md | markdown | 6.1 KB |
| references/lean-startup-anti-patterns.md | markdown | 6.2 KB |
| scripts/lean_canvas_validator.py | script | 13.0 KB |
references/lean-canvas-framework.md
View on GitHub# Lean Canvas — Framework Reference
Ash Maurya's adaptation of BMC for startups.
## 1. Why a different canvas?
BMC works for established businesses. Startups face different uncertainty:
- Problem is uncertain (does anyone have it?)
- Solution is uncertain (does it actually solve the problem?)
- Channel is uncertain (can we reach customers economically?)
- Revenue model is uncertain (will they pay?)
Lean Canvas surfaces these uncertainties. BMC papers over them.
## 2. The 9 blocks in working depth
### Block 1 — Problem
List the **top 1-3 problems** the customer faces. Plus:
**Existing alternatives** — how do customers solve this today?
The existing-alternatives sub-block is critical. Customers always have a
workaround (spreadsheet, manual process, competing product, doing nothing).
Naming it tells you:
- The bar your product must clear
- The price they currently pay (in time, money, frustration)
- Your switching cost narrative
Common errors:
- Listing 10 problems (lose focus)
- "Inefficiency" as a problem (not specific)
- No existing alternative (always exists; find it)
### Block 2 — Customer Segments
Especially: **Early Adopters**. The first paying customers — those who
are most actively seeking what you're building.
Early Adopters:
- Know they have the problem
- Have tried alternatives
- Are willing to pay for a better solution
- Will give honest feedback
- May not be your eventual mainstream segment
Common errors:
- "Tech-forward enterprises" — too vague
- "Anyone who needs X" — no specificity
- Confusing user with buyer (especially B2B)
### Block 3 — Unique Value Proposition (UVP)
Single, clear, compelling message that turns visitors into prospects.
Template: "**[High-level outcome]** for **[early adopter segment]** that
**[differentiator from existing alternatives]**."
Example: "Cut SOC 2 audit prep from 6 months to 6 weeks for mid-market
SaaS — by automating 80% of the evidence collection your auditor asks for."
Common errors:
- "World-class X for everyone" (vague)
- Feature list (not value)
- "Better, faster, cheaper" (everyone's pitch)
- > 1 sentence (becomes a paragraph; nobody reads)
### Block 4 — Solution
Top 1-3 features (NOT 10). Each feature maps to a Problem.
A Solution block with 8 features signals founder lost discipline.
Bring it back to "what does this product *do* in 3 bullets?"
Common errors:
- Feature list of everything possible
- Solution that doesn't map to the listed Problems
- Solution before Problem (solution-in-search-of-problem)
### Block 5 — Channels
Path(s) to reach customers. For startups, focus on channels you can
test cheaply in weeks:
- Founder-led sales (calls, conferences)
- Content (one piece per week, measured)
- Community engagement (Slack, Discord, subreddit)
- Direct outreach (cold email, LinkedIn)
- Paid acquisition (small budget, test)
Common errors:
- "Online marketing" (not specific)
- All channels listed = no channel tested
- Listing channels you can't yet afford
- No CAC estimate
### Block 6 — Revenue Streams
Revenue model + LTV + forecast.
For startups, capture:
- **Pricing model:** freemium / subscription / usage / transaction
- **Price point:** specific number (even if hypothesis)
- **LTV estimate:** months × MRR × gross margin (rough)
- **First $X thousand revenue plan:** how do you get to $10K MRR?
Common errors:
- "TBD" (decide; can iterate)
- LTV stacked on LTV stacked on LTV (every assumption inflated)
- Free forever model with no path to monetize
### Block 7 — Cost Structure
CAC + distribution + people + hosting.
For a startup, distinguish:
- **Fixed monthly burn** (people, tools, infra at zero customers)
- **Variable per-customer cost** (CAC, support, infra)
- **Capital-intensive items** (if any)
Common errors:
- Forgetting CAC (the biggest cost line)
- Generic "salaries, rent, marketing"
- Ignoring infrastructure scaling cost
### Block 8 — Key Metrics
The key activities you measure (and a single one to optimize for).
Pirate metrics (AAARRR):
- Acquisition
- Activation
- Retention
- Referral
- Revenue
- (or shift to Engagement first)
Pick **one** as North Star. Others are inputs.
Common errors:
- 12 metrics tracked, nothing optimized
- "Revenue" as North Star (lagging)
- Metrics that don't tie to value delivered
### Block 9 — Unfair Advantage
Something that cannot be easily copied or bought.
Maurya: "A real unfair advantage is something that cannot be easily
copied or bought."
What counts:
- Insider information (proprietary data, deep customer relationships)
- Authority / dream team (recognized expertise)
- Personal endorsements / network
- Existing customers / community
- Network effects already started
- Patented IP
What doesn't count:
- "We move fast"
- "Better UX"
- "Our team is great"
- "First mover" (in most cases)
- "AI" / "ML" (commodity now)
- "Cheaper" (race to zero)
Most startups have NO unfair advantage at start. The honest play:
mark "none yet — will build via [X]" and explicitly plan to acquire one.
## 3. The early-adopter test
A useful test for whether Lean Canvas is grounded:
**Name 5 specific early adopters by name + their existing alternative.**
If you can't, you're not at problem-solution fit. The canvas is hypothesis,
not validation.
## 4. Assumption register
Every Lean Canvas implies assumptions. List the riskiest:
| Block | Assumption | Risk | Evidence | Test |
|-------|------------|------|----------|------|
| Problem | Segment X has this problem with frequency Y | high | low | 10 customer interviews |
| Channel | Cold outreach converts at 2% | high | none | 100-email test |
| Revenue | Segment X will pay $50/mo | high | low | landing page + waitlist |
Test the highest risk + lowest evidence first.
## 5. When to update the canvas
- Every quarter (refresh)
- After major experiments (incorporate learnings)
- After pivots (new canvas; archive old)
- Before fundraising (investor-facing version)
- Before strategic offsite (working version)
A static Lean Canvas signals lack of learning.
## 6. The 1-page rule
Lean Canvas must fit on 1 page. If you can't:
- Your Solution has too many features
- Your Problem list is too long
- Your UVP isn't sharp
Force the discipline. Excess prose hides muddled thinking.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |