Glossary

What Is the Lean Startup Method?

Updated November 13, 2026 · Team Fonda

Short answer

Lean startup is a method for starting a business by treating your idea as a set of guesses and testing the riskiest ones with small, cheap experiments. You build the smallest thing that can teach you something, measure how real customers react, and then decide whether to keep going or change direction.

Key takeaways

The core loop is build, measure, learn. The goal of each turn is learning, not shipping features.
You test with a minimum viable product, which can be a landing page, a manual service or a rough prototype.
Set the pass mark before you run a test, so the result tells you to persevere or pivot.
Lean does not mean cheap or low quality. It means not spending on things you have not yet proven customers want.

What lean startup means in plain words

A new business plan is mostly guesses: who the customer is, what problem they have, what they will pay. The lean startup method, made popular by Eric Ries in his book The Lean Startup, says you should find out which guesses are wrong as early and as cheaply as you can.

The opposite approach is to spend months building a finished product in private and then launch it. If a key guess was wrong, you find out after the money and time are gone. Lean startup moves that discovery to the front.

How the build, measure, learn loop works

The loop

Guess (hypothesis) -> Build the smallest test -> Measure what customers do -> Learn -> Persevere or pivot

Write down your riskiest guess. For example: "Owners of small gyms will pay for a tool that fills empty class slots." A lean canvas helps you list all your guesses on one page.
Build the smallest test. This is your minimum viable product. It only needs to be good enough to test the guess.
Measure behavior, not opinions. Sign-ups, pre-orders and repeat use count for more than people saying "nice idea".
Learn and decide. If the result beats the pass mark you set, keep going. If not, change one part of the plan, which is called a pivot, and test again.

A worked example

This is an illustration with made-up numbers. Say you want to build a tool that chases late invoices for freelance designers. Your riskiest guess is that designers will pay $10 a month to have reminders sent for them.

Test: a one-page site that describes the tool and offers a pre-order, plus posts in two freelance design communities. No software yet.
Pass mark, set in advance: at least 5 pre-orders from the first 200 visitors.
Result: 200 visitors, 31 email sign-ups, 2 pre-orders.
What you learn: people are interested but few will pay. You call ten of the sign-ups and hear that sending a reminder is not the hard part. The late payers are clients who never agreed payment terms, so there is nothing firm to chase.
Decision: pivot the idea toward contract and deposit templates that set payment terms before the work starts, and run a new test.

The whole cycle took two weeks and very little money. Building the reminder tool first would have taken months and taught you the same thing.

Why it matters for a first-time founder

You meet lean startup at the very start, between having an idea and building anything. It matters most when you are working with savings or building on the side, because every month you spend on the wrong thing is a month of runway you do not get back.

The method also gives you a clear order of work: validate the idea, then build an MVP, then look for product-market fit. Fonda follows the same order. You talk to real customers in the Validate phase and get a Verdict of go, refine or pivot before you reach the business plan.

Common mistakes

Calling a small product an MVP when it tests nothing. If you cannot say which guess it tests, it is just a small product.
Setting the pass mark after you see the result. Almost any number looks fine in hindsight.
Asking friends. They want to be kind. Test with strangers who have the problem.
Pivoting every week. Give each test enough people and time to mean something.
Using lean as a reason to ship something broken. The test must work well enough that a no means no to the idea, not no to the bugs.

Customer discovery: the interviews you run before you build a test.
Problem-solution fit: proof that your solution answers a problem people care about.
Idea validation: the wider process of checking an idea before you commit.

Frequently asked questions

Is lean startup only for tech companies?

No. A bakery can sell at a weekend market before signing a lease, and a consultant can sell one pilot project before building a website. Any business with unproven guesses can test them small first.

What is the difference between lean startup and agile?

Agile is a way for a team to build software in short cycles. Lean startup is a way to decide what is worth building at all. Many teams use both: lean to choose the direction, agile to do the work.

Do I still need a business plan if I use lean startup?

Often yes, but later. Test the idea first, then write the plan with what you learned. A plan built on tested guesses is easier to defend to a bank or an investor.

How long should one build, measure, learn cycle take?

As short as you can make it while still getting a clear answer. For an early idea, a test that runs for days or a couple of weeks is common. If a cycle needs months, look for a smaller test.