ENTREPRENEURSHIPMonths to result

The 12 Startups in 12 Months Challenge

Maximize success odds through rapid sequential experimentation at scale

Problem it solves

business growth stalls

Best for

Developers and creators who tend to over-plan and under-execute or who struggle to find product-market fit

Not ideal for

People building complex enterprise products that require deep specialization or long sales cycles

Overview

Why this framework exists

The 12 Startups in 12 Months challenge pioneered by Pieter Levels is a structured approach to entrepreneurial experimentation that forces rapid execution and market validation. The premise is simple: commit to launching one new product every month for a year. Most will fail and that is the point. By dramatically increasing your number of attempts while compressing the timeline for each you maximize your chances of finding something that works while building crucial skills in shipping marketing and iterating. This framework directly combats perfectionism and fear of failure by making failure the expected default outcome for any individual project. The focus shifts from making any single project succeed to building a portfolio of experiments from which winners emerge organically.

Core principles

4 total
  1. Volume of attempts matters more than quality of any single attempt
  2. Public commitment creates accountability that overcomes procrastination
  3. Time constraints force focus on essential features only
  4. Failure is data not defeat and each failed project teaches something valuable

Steps

4 steps
  1. Commit Publicly to the Challenge
    Announce your 12-in-12 challenge publicly on social media or your blog or to your community. The public commitment creates external accountability that makes it much harder to quit when things get difficult. Set clear rules for what counts as a launch and it must be live and accessible to users.
    Pro tipCreate a simple tracking page or blog series to document each launch as this content itself becomes valuable.
    WarningDo not set the bar too high for what counts as a launch.
  2. Generate and Prioritize Ideas Quickly
    Spend no more than one day brainstorming and selecting each month's project. Draw from personal pain points and trends you observe and requests from your audience. Rank ideas by how quickly you could build a minimum version and how easily you could validate demand. Choose the one you can ship fastest.
    Pro tipKeep a running ideas list throughout the year so you are never starting from zero.
  3. Build and Launch Within the Month
    Spend the first three weeks building and the last week preparing for launch. Use familiar tools and technologies exclusively. Cut any feature that is not absolutely necessary for a user to experience the core value proposition. Launch on multiple platforms simultaneously.
    Pro tipSet a hard internal deadline of day 21 for feature-complete leaving the final week for testing and launch preparation.
    WarningResist the urge to delay launch because the product is not perfect.
  4. Evaluate and Move On or Double Down
    After launch monitor key metrics for the remaining days of the month. Look for signs of organic traction such as people using it without being prompted or sharing it or willing to pay. If yes continue developing it alongside new monthly projects. If no document what you learned and move on without guilt.
    Pro tipSet specific quantitative thresholds before launch that will determine whether you continue or move on.

Checklist

Saved in your browser

Examples

1 cases
Pieter Levels Original 12 Startups

Levels publicly committed to and executed the original 12-in-12 challenge in 2014. He launched projects ranging from a chat roulette for music to a remote job board. Most gained little traction but NomadList and RemoteOK emerged as winners eventually generating millions in combined annual revenue.

OutcomeTwo businesses from the portfolio became million-dollar revenue generators
Documented on levels.io blog and discussed in the My First Million episode

Common mistakes

3 traps
Making Each Project Too Ambitious
The most common failure mode is scoping projects too large for a single month. Each project should be achievable by one person in three weeks of focused work.
Not Launching Publicly
Building things without putting them in front of real users defeats the entire purpose. Every project must be publicly accessible and actively shared with potential users.
Getting Emotionally Attached to Failed Projects
The framework requires letting go of projects that do not find traction. Spending extra months trying to force a failed project to work negates the volume advantage.

Origin story

How this framework came to be

In 2014 Pieter Levels was frustrated with his inability to finish and launch projects. Like many developers he would start building something and get bogged down in features and perfectionism and eventually abandon the project before it ever launched. He decided to flip the script by publicly committing to launching 12 startups in 12 months and documenting the entire process. The public accountability and fixed deadline forced him to strip away everything non-essential. Most of the 12 projects went nowhere but two NomadList and RemoteOK became highly profitable businesses.

Source

Traced to primary
Source · PODCAST
This Is What Real Freedom Looks Like
Pieter Levels · 2022
Open source →