agentleFS
yuusakuriyuusakuri/agent-skills/skills/lean-canvas/SKILL.md

lean-canvas

Skill2 starsChanged 10 days agoMITView on GitHub

Generate a Lean Canvas with problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue. Use when exploring a lean startup canvas, testing a business hypothesis, or modeling a new venture.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Missing strategic sections: No vision (why should your team wake up every day?), no trade-offs (what you choose NOT to do), no relative …

    line 102
  2. Distinctive:

    Update the canvas as you learn and validate

    line 113

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Lean Canvas

Metadata

  • Name: lean-canvas
  • Description: Generate a Lean Canvas business model with detailed sections for problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue.
  • Triggers: lean canvas, startup canvas, lean model, business hypothesis

Instructions

You are a business model strategist designing a Lean Canvas for $ARGUMENTS.

Your task is to create a comprehensive Lean Canvas that outlines the business hypothesis and key business model assumptions for the product.

Input Requirements

  • Product or feature description
  • Target customer segment(s)
  • Market context and problem space
  • Any available metrics or business constraints

Lean Canvas Template

Section 1: Product Definition

1. Problem

  • Top 3 customer problems or needs
  • Customer pains and frustrations
  • Current unsatisfactory solutions

2. Solution

  • Top 3 features or approaches
  • How each feature addresses the problem
  • Why this solution is novel or better

3. Unique Value Proposition (UVP)

  • Concise, memorable statement
  • Why customers choose you over alternatives
  • What makes you different (not just "better")

4. Unfair Advantage

  • What defensibility exists?
  • Barriers to competition (network effects, brand, IP, switching costs)
  • What competitors can't easily replicate

Section 2: Market & Traction

5. Customer Segments

  • Who is the target customer?
  • Early adopters and first segment
  • Customer personas or archetypes
  • How large is the addressable market?

6. Channels

  • How do you reach customers?
  • Primary acquisition channels
  • Distribution and sales approach
  • How do customers find you?

7. Revenue Streams

  • How do you make money?
  • Pricing model or revenue per customer
  • Customer lifetime value (LTV)
  • Revenue growth assumptions

Section 3: Economics & Validation

8. Cost Structure

  • Fixed costs (salaries, infrastructure, facilities)
  • Variable costs (COGS, transaction costs, support)
  • Key cost drivers
  • Cost per customer acquisition (CAC)

9. Key Metrics

  • Activation: How do users get value quickly?
  • Retention: How many users stick around?
  • Revenue: How do we measure financial success?
  • North Star metric for the business

Output Process

  1. Define the core problem(s) being solved
  2. Outline 2-3 solution approaches
  3. Craft a compelling UVP
  4. Identify what creates competitive advantage
  5. Target 1-2 customer segments
  6. Map acquisition channels
  7. Define revenue model and pricing
  8. Estimate cost structure
  9. Identify 3-5 critical metrics to track
  10. Surface key assumptions and hypotheses
  11. Suggest validation experiments (landing page, interviews, MVP)

Domain Context

Lean Canvas vs Business Model Canvas vs Startup Canvas:

Lean Canvas (Ash Maurya) is a startup-focused adaptation of the Business Model Canvas that replaces Partners/Activities/Resources with Problem/Solution/Unfair Advantage. It's fast and hypothesis-driven, but has known limitations:

  • Redundancy: "Problem" overlaps with Market Segments (markets are defined by problems/JTBD), and "Solution" overlaps with Value Proposition (which by definition includes features). This can create confusion about what goes where.
  • Missing strategic sections: No vision (why should your team wake up every day?), no trade-offs (what you choose NOT to do), no relative costs (low cost vs unique value positioning), no key metrics.
  • Narrow defensibility: "Unfair Advantage" focuses on one defensive element, but strong strategy is hard to copy as an integrated whole — not because of a single advantage.
  • No coherence check: Doesn't address whether all strategic choices reinforce each other.

When to use Lean Canvas: Quick hypothesis testing when you need speed over completeness. Best as a brainstorming tool, not a strategy document.

Consider instead: Startup Canvas (Paweł Huryn) separates strategy (9 sections from the Product Strategy Canvas) from business model (Cost Structure + Revenue Streams). Recommended when you need both strategic clarity AND a business model for a new product.

Notes

  • The Lean Canvas is designed for rapid hypothesis testing
  • Focus on addressing the riskiest assumptions first
  • Update the canvas as you learn and validate
  • Each section should be specific and measurable where possible
  • This canvas helps align founding teams on business strategy

Further Reading

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.