lean-canvas

Imported from borghei/claude-skills (project-management/strategy-frameworks/lean-canvas/SKILL.md). Install upstream with npx skills add borghei/claude-skills --skill lean-canvas. Copyright stays with the author (MIT + Commons Clause).

Lean Canvas

A 9-block startup canvas adapted from BMC. Replaces 4 BMC blocks (Key Resources, Activities, Partnerships, Customer Relationships) with startup-focused ones (Problem, Solution, Key Metrics, Unfair Advantage).

When to use this skill

• Early-stage (pre-PMF) product or company
• Capturing assumptions that need testing
• 20-minute model sketch (BMC takes longer)
• Pivot conversations — what would change?
• Stress-testing unfair advantage before building

The 9 Lean Canvas blocks

1. Problem — Top 3 problems for the segment
2. Customer Segments — Target customers (especially Early Adopters)
3. Unique Value Proposition — Single, clear, compelling message
4. Solution — Top 3 features that solve the problems
5. Channels — Path to customers
6. Revenue Streams — Revenue model + LTV + revenue forecast
7. Cost Structure — Customer acquisition cost + distribution + people + hosting
8. Key Metrics — Key activities you measure
9. Unfair Advantage — Something that cannot be easily copied or bought

Lean Canvas vs BMC

Same outer shape; different inner emphasis. Use Lean when problem + unfair advantage matter more than ops detail.

Clarify First

Before building the canvas, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

• The specific early-adopter segment: named, not "everyone" (the Problem, UVP, and Channels blocks all hinge on a concrete early adopter).
• The top 3 problems: for that segment (the Problem block; if you can't name them you have an idea, not a startup).
• Existing alternatives: how customers solve this today (signals whether the problem is real; "they live with it" is important signal).

Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.

Workflow

Step 1 — Problem-Segment first

Start with Problem and Customer Segments. If you can't list the top 3 problems for a specific segment, you don't have a startup — you have an idea.

Step 2 — Existing alternatives

Within Problem block, list how customers solve this today. If the answer is "they don't / they live with it," that's important signal.

Step 3 — Unique Value Proposition

A single sentence that:

• Names the early-adopter segment
• States the differentiating outcome
• Distinguishes from existing alternatives

Template: "[Outcome] for [segment] that [differentiator]."

Step 4 — Solution (3 features max)

Limit to 3. Founders always want to list 10. Resist.

Step 5 — Unfair Advantage

The hardest block. What do you have that no one can easily copy?

• Insider information / domain
• Personal authority / reputation
• Dream team
• Personal endorsements
• Existing customer base
• Network effects already in motion
• Patented IP

If empty: most startups have nothing yet. Mark explicitly + plan how to build one.

Step 6 — Channels, Revenue, Costs, Metrics

Fill remaining blocks. Be specific.

Step 7 — Run lean_canvas_validator.py

Audit for: missing blocks, generic content, no early adopter named, no existing alternatives, no Key Metrics, vague Unfair Advantage.

python3 project-management/strategy-frameworks/lean-canvas/scripts/lean_canvas_validator.py \
  --input canvas.json --format markdown

Decision frameworks

Lean Canvas vs BMC — when to use which

Early adopter heuristic

Early adopters are not "future mainstream users." They are:

• Aware they have the problem
• Actively looking for a solution
• Have cobbled together a workaround (existing alternative)
• Have budget / authority to try yours

If you can't name 5 specific early adopters by name + workaround, you're not at problem-solution fit yet.

Unfair Advantage — what counts

Counts:

• Insider information (proprietary data, deep customer relationships)
• Personal authority (industry-recognized expertise)
• Existing community / audience
• Network effects already started
• Capital + brand recognition

Doesn't count:

• "We work harder"
• "Our team is great"
• "First mover" (in most cases; usually replicable)
• "Better UX" (replicable)
• "AI" (everyone has AI now)
• "Cheaper" (price competition is a race to zero)

If your only unfair advantage is "speed" or "execution," that's a weakness as a moat.

Common engagements

"Help me sketch a canvas for my new idea"

1. Problem + Segment first.
2. Force list the existing alternatives (and what they cost).
3. Write the UVP (one sentence).
4. List Solution as 3 features max.
5. Identify Channels you can realistically test in 4 weeks.
6. Stub Revenue + Cost + Metrics.
7. Honest Unfair Advantage assessment.
8. Identify top 3 riskiest assumptions; design test for each.

"Should we pivot?"

1. Build current state Lean Canvas.
2. Build proposed state Lean Canvas.
3. Compare: what's different? what's the unfair advantage now?
4. What evidence do we have that the new model works?
5. Run the assumption-test for the riskiest new assumption.

Anti-patterns to avoid

• Solution before Problem. Solution-in-search-of-problem.
• "Everyone" as segment. Force a specific early adopter description.
• No existing alternative listed. Customers always do something today.
• UVP that says everything. Says nothing.
• 5+ solution features listed. Pick 3 max.
• Vague Key Metrics. Pirate metrics (AAARRR) or HEART or similar.
• Unfair Advantage = "execution". Not an advantage.
• No assumption register. Canvas isn't a plan, it's a hypothesis.

Scope & Limitations

In Scope:

• A nine-block Lean Canvas: Problem, Customer Segments, Unique Value Proposition, Solution, Channels, Revenue Streams, Cost Structure, Key Metrics and Unfair Advantage
• Problem and early-adopter work first, including existing alternatives and named early adopters
• Tests for what counts as an unfair advantage and when to use Lean Canvas instead of the Business Model Canvas
• A canvas audit for missing blocks, generic content, no named early adopter, no existing alternatives, missing Key Metrics and a vague Unfair Advantage (lean_canvas_validator.py)
• Current-state versus proposed-state canvases for pivot conversations

Out of Scope:

• Operating-scale business models with partners, resources and activities (see project-management/strategy-frameworks/business-model-canvas/)
• Deep work on the value proposition (see project-management/discovery/value-proposition-canvas/)
• Building a full assumption register (see project-management/discovery/identify-assumptions/)
• Defining the Key Metric as a North Star (see project-management/execution/north-star-metric/)
• Financial forecasts behind the revenue and cost blocks (see finance/financial-analyst/)

Important Caveats:

• lean_canvas_validator.py reads a hand-written JSON canvas. Flags such as names_segment and names_differentiator are self-reported.
• The tool checks structure and specificity, not whether the problems are real. That needs customer evidence.
• A Lean Canvas is a set of hypotheses, not a plan. It goes stale as soon as tests come back.

References

• references/lean-canvas-framework.md — the 9 blocks deep, comparison to BMC
• references/lean-startup-anti-patterns.md — common mistakes + worked fixes

Related skills

• project-management/strategy-frameworks/business-model-canvas — operating-scale variant
• project-management/discovery/value-proposition-canvas — deeper on UVP
• project-management/discovery/identify-assumptions — assumption register
• project-management/discovery/pre-mortem — risk discovery
• project-management/execution/north-star-metric — Key Metric definition
• c-level-advisor/ceo-advisor — strategic context