---
name: lean-startup-method
description: Apply the Build-Measure-Learn feedback loop to validate business hypotheses with minimum viable products. Use when the user asks about lean startup, MVP design, validated learning, build-measure-learn, or whether to pivot or persevere.
triggers:
  - "lean startup"
  - "MVP"
  - "validated learning"
  - "build measure learn"
  - "pivot or persevere"
disable-model-invocation: false
title: lean-startup-method
canonical_url: https://skilld.dev/gh/salikshah/startup-agent-skills/lean-startup-method
last_updated: 2026-10-29T10:46:09.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [evals/evals.json](https://skilld.dev/api/skills-raw/salikshah/startup-agent-skills/lean-startup-method/evals/evals.json).
>
> If the user asked to install this Skill, run `npx skilld install salikshah/startup-agent-skills/lean-startup-method`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/lean-startup-method`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/salikshah/startup-agent-skills/lean-startup-method) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/lean-startup-method`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/lean-startup-method --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/lean-startup-method --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Lean Startup Method

## Intent
Use Eric Ries's Build-Measure-Learn loop to systematically test business hypotheses and determine whether to pivot or persevere. Apply this skill when launching a new product, entering a new market, or facing uncertainty about customer demand.

## Inputs
- Business idea or hypothesis statement
- Target customer segment definition
- Key assumptions (value hypothesis, growth hypothesis)
- Available resources and timeline
- Current stage of product development

## Process (SOP)
1. Step 1: Identify the riskiest assumption underlying your business idea (often the value hypothesis — will customers actually use/buy this?).
2. Step 2: Define a Minimum Viable Product (MVP) that tests that single assumption with minimum effort — strip every feature that does not directly serve the learning goal.
3. Step 3: Define the metric that will measure success before building anything (e.g., conversion rate, retention cohort, willingness-to-pay signal).
4. Step 4: Build the MVP in the shortest possible cycle — days or weeks, not months.
5. Step 5: Deploy the MVP to a small, representative cohort of real customers (not friends and family).
6. Step 6: Measure actual behavior against the pre-registered metric using innovation accounting (cohort-based analysis, not vanity metrics).
7. Step 7: Analyze results to determine whether the hypothesis is validated, invalidated, or inconclusive.
8. Step 8: Decide: pivot (change one or more hypotheses while keeping learned insights) or persevere (continue optimizing the same fundamental strategy).
9. Step 9: Document what was learned in a structured format — hypothesis → test → result → decision — so knowledge compounds across iterations.
10. Step 10: Repeat the loop, progressively increasing investment only as validation accumulates.

## Outputs
- A tested MVP deployed to real customers
- A clear pivot-or-persevere decision backed by cohort data
- A documented learning log of validated and invalidated hypotheses
- Reduced waste from building features nobody wants

## Evidence
Source: "The Lean Startup" by Eric Ries. Key concepts: Build-Measure-Learn loop, MVP definition, validated learning, innovation accounting, pivot vs. persevere, vanity metrics vs. actionable metrics, cohort analysis.

## Examples
A SaaS startup wants to test demand for an AI-powered invoicing tool. They skip the full product and build a concierge MVP: manually process invoices for 10 small businesses behind a single landing page. When 7 of 10 sign up for the paid waitlist, the value hypothesis is validated and they proceed to build the product.

## Metrics
- Time per Build-Measure-Learn cycle (target: under 2 weeks)
- Number of hypotheses validated vs. invalidated per quarter
- Customer retention cohort curves (flattening or declining)
- Percentage of roadmap driven by validated learning vs. speculation

## Anti-Patterns
- Building a "minimum" product that is actually bloated with unnecessary features
- Measuring vanity metrics (total signups, page views) instead of actionable cohort metrics
- Pivoting too early based on inconclusive data from too few customers
- Pivoting too late, refusing to abandon a failing strategy despite evidence
- Calling a pivot a failure instead of a strategic redirection
- Running multiple concurrent experiments without isolating variables
