Test Small, Learn Fast: Lean Startup Ideas for a One-Person Business

Look for the assumption most likely to be wrong

Lean Startup is a way of developing a new product by testing it in small steps, learning from what customers actually do, and adjusting before you have spent much. Eric Ries described it in his 2011 book The Lean Startup. For a freelancer or a small company, the practical benefit is simple: you find out sooner, and at lower cost, when an idea does not work.

The starting point is to treat your idea as a bundle of hypotheses. These customers have this problem. They will pay this much. They will find me this way. Each of these is a guess you have not yet checked. Pick the guess that, if wrong, would sink the whole plan, and test that one first.

The build-measure-learn loop

The core of the method is a loop with three steps.

• Build the smallest thing that can test your hypothesis.
• Measure what customers actually do with it.
• Learn whether to keep going, adjust, or change direction.

What matters is how quickly you complete one pass. Running the loop more often teaches you more than polishing any single version.

Ries calls the smallest test version a minimum viable product, or MVP. It does not mean a stripped-down finished product. It means the version that takes the least effort while still producing a real answer.

A test does not have to be a working product

An MVP is not the same as building the app first. For a small business, one of these may be enough:

• A single page describing the offer, with a sign-up button, so you can count clicks.
• Taking orders first and delivering the service by hand behind the scenes.
• A short guide handed out in exchange for an email address, to see who asks for it.
• Asking ten people directly whether they would reserve a spot and pay in advance.

Ries's book describes cases like these, where demand was tested through a simple demonstration or where the work was done manually at first. It may look rough, but it still shows whether customers will spend money or time.

Measure actions, not opinions

Decide what counts as success before you run the test. If you set the bar after seeing results, it is easy to read them the way you hoped.

For example, write down in advance what share of visitors must click the sign-up button for you to continue. Base that number on your own scale and history rather than borrowing someone else's average.

Opinions and behavior differ. "That sounds great" does not mean someone will buy. Record moments when the other person gave something up: a sign-up, an inquiry, a booking, a deposit.

Continue, change, or stop

After one pass you have three choices. If the results support the hypothesis, continue. If part of it failed, change one thing, such as the customer, the price, or the delivery method, and test again. If results fall well short and you see no clear way to fix them, stopping is a legitimate decision.

Ries calls a change of direction a pivot. The point is to treat it as a result of learning, not as a failure.

Be careful not to conclude too much from a few reactions. With small samples, treat the result as a sign of whether the idea is worth pursuing, not as proof.

Common missteps for a small business

The most frequent one is polishing the prototype so long that you burn your time and energy before learning anything. Set a deadline before you test and ship whatever form is ready by then.

Another is counting friends' compliments as demand. Kind words and paying are different behaviors. Record separately whether strangers responded.

Changing several things at once hides what worked. In a single test, change only one of price, wording, or target customer.

Write down a few lines after each test: what you tried and what you learned. Without notes, you may repeat the same test six months later.

If your test involves taking payment in advance, rules on disclosures and refunds may apply. Check with a professional depending on what you sell.

Choosing what to test first

When you cannot decide where to start, begin with something that would cost a lot if wrong but is easy to check. Whether anyone wants the product at all can be tested before you build it. Fine adjustments to price or delivery can wait until demand is confirmed.

If you work alone, run only one or two tests at a time. Too many at once blur which result came from which test and spread your time thin.

What to do next

1. Write your current idea as four hypotheses: customer, problem, price, and how people will find you.
2. Choose the one that would break the plan if wrong.
3. Decide the cheapest way to test it. A single page, ten conversations, or delivering by hand are all acceptable.
4. Before testing, write down in numbers what result would make you continue.
5. Run the test within two weeks, then decide: continue, change, or stop.

Keep the test period short. The longer it runs, the harder it becomes to know when to quit.